Harq rtt timer adjustment for multi-tb scheduling

ABSTRACT

Methods of operating a wireless device in a communication network are provided. Such methods include receiving a scheduling message that includes a schedule identifying a plurality of transmission blocks, TBs and determining a quantity of the plurality of TBs that are identified in the scheduling message. Methods may include determining a quantity of Hybrid Automatic Repeat Request Acknowledgement, HARQ ACKs in an ACK bundle identified in the scheduling message and dynamically generating an acknowledgement timer value that corresponds to the quantity of the plurality of TBs and the quantity of HARQ ACKs in the ACK bundle.

FIELD

The present disclosure relates generally to communications, and moreparticularly to communication methods and related devices and nodessupporting wireless communications.

BACKGROUND

A simplified wireless communication system is illustrated in FIG. 1 .The system includes a UE 100 that communicates with one or more accessnodes 210, 220 using radio connections 107, 108. The access nodes 210,220 are connected to a core network node 106. The access nodes 210-220are part of a radio access network 105.

Current solutions do not address the case when one downlink controlindication, DCI, schedules multiple Transmission Blocks, TBs, for a userequipment, UE. Thus, (uplink/downlink) hybrid automatic repeat request,HARQ, round trip time, RTT, timer values may be too short for multipleTB transmissions, and may run out before all HARQ acknowledgements,ACKs, have been transmitted fully. When a HARQ RTT timer runs out,retransmission timer is started, during which UE monitors forretransmissions. However, since the UE may not have been able totransmit all HARQ ACKs during a HARQ RTT timer, the UE may be listeningfor retransmissions in vain, thus wasting power.

Current solutions do not take into account the case of a bundled HARQACK.

SUMMARY

Some embodiments herein are directed to methods of operating a wirelessdevice in a communication network. Methods may include receiving ascheduling message that includes a schedule identifying multipletransmission blocks, determining a quantity of the TBs that areidentified in the scheduling message, and dynamically generating anacknowledgement timer value that corresponds to the TBs.

In some embodiments, dynamically generating the acknowledgement timervalue includes generating an acknowledgment timer value that is afunction of the quantity of the transmission blocks.

Some embodiments provide that the scheduling message includes a downlinkcontrol indication, DCI. In some embodiments, dynamically generating theacknowledgement timer value includes multiplying a portion of a timervalue by the quantity of TBs in the scheduling message.

In some embodiments, the acknowledgement timer value includes a HybridAutomatic Repeat Request Round Trip Time, HARQ RTT, timer value that isgenerated as 7+l*N in which N is a Physical Uplink Control Channel,PUCCH, repetition factor and l is the quantity of TBs identified in thescheduling message.

In some embodiments, the acknowledgement timer value includes a HybridAutomatic Repeat Request Round Trip Time, HARQ RTT, timer value that isgenerated as 7+l*N+s in which N is a Physical Uplink Control Channel,PUCCH, repetition factor, l is the quantity of the plurality of TBsidentified in the scheduling message and s is a delay factor thatprovides timer alignment corresponding to machine type communicationphysical downlink control channel, MPDCCH, operations.

Some embodiments provide that the scheduling message includes a firstscheduling message, the TBs include first TB's, the quantity of TB'sincludes a first quantity of TBs, and the acknowledgement timer valueincludes a first acknowledgement timer value. In such embodiments,operations further include receiving a second scheduling message thatincludes a second schedule identifying a second set of multiple TBs,determining a second quantity of TBs that are identified in the secondscheduling message, and dynamically generating a second acknowledgementtimer value that corresponds to the second set of TBs and that isdifferent from the first acknowledgement timer value.

In some embodiments, the communication network includes a narrow bandinternet of things network, NBIoT. Some embodiments provide that thecommunication network includes an enhanced Machine Type Communication,eMTC, network.

Some embodiments disclosed herein include methods of operating a radioaccess network node, RAN, in a communication network. Methods mayinclude sending, to a UE, a scheduling message that includes a scheduleidentifying multiple transmission blocks and that causes the UE todetermine a quantity of the TBs that are identified in the schedulingmessage and to dynamically generate an acknowledgement timer value thatcorresponds to the TBs.

In some embodiments, the acknowledgement timer value is a function ofthe quantity of transmission blocks. In some embodiments, the schedulingmessage includes a downlink control indication, DCI. As used herein, theterm downlink control indication, DCI, may also include, comprise and/orbe used interchangeably with the term downlink control information,which is a term that is well known to those having skill in the relevantfield. Some embodiments provide that the acknowledgement timer valueincludes a product from multiplying a portion of a timer value by thequantity of TBs in the scheduling message.

In some embodiments, the acknowledgement timer value includes a HybridAutomatic Repeat Request Round Trip Time, HARQ RTT, timer value that isgenerated as 7+l*N in which N is a Physical Uplink Control Channel,PUCCH, repetition factor and l is the quantity of TBs identified in thescheduling message.

In some embodiments, the acknowledgement timer value includes a HybridAutomatic Repeat Request Round Trip Time, HARQ RTT, timer value that isgenerated as 7+l*N+s in which N is a Physical Uplink Control Channel,PUCCH, repetition factor, l is the quantity of the plurality of TBsidentified in the scheduling message and s is a delay factor thatprovides timer alignment corresponding to machine type communicationphysical downlink control channel, MPDCCH, operations.

Some embodiments provide that the scheduling message is a firstscheduling message, the multiple TBs include a first plurality of TB's,the quantity of TB's includes a first quantity of TBs, and theacknowledgement timer value includes a first acknowledgement timervalue. In such embodiments, the UE is further caused to receive a secondscheduling message that includes a second schedule identifying a secondplurality of TBs; determine a second quantity of TBs that are identifiedin the second scheduling message, and dynamically generate a secondacknowledgement timer value that corresponds to the second plurality ofTBs and that is different from the first acknowledgement timer value.

In some embodiments, the communication network includes a narrow bandinternet of things network, NBIoT. Some embodiments provide that thecommunication network includes an enhanced Machine Type Communication,eMTC, network.

Some embodiments are directed to methods of operating a core networknode in a communication network. Methods may include sending, to a UE, ascheduling message that includes a schedule identifying multipletransmission blocks and that causes the UE to determine a quantity ofthe TBs that are identified in the scheduling message and to dynamicallygenerate an acknowledgement timer value that corresponds to the TBs.

In some embodiments, the acknowledgement timer value is a function ofthe quantity of transmission blocks. In some embodiments, the schedulingmessage includes a downlink control indication, DCI. Some embodimentsprovide that the acknowledgement timer value includes a product frommultiplying a portion of a timer value by the quantity of TBs in thescheduling message.

In some embodiments, the acknowledgement timer value includes a HybridAutomatic Repeat Request Round Trip Time, HARQ RTT, timer value that isgenerated as 7+l*N in which N is a Physical Uplink Control Channel,PUCCH, repetition factor and l is the quantity of TBs identified in thescheduling message.

In some embodiments, the acknowledgement timer value includes a HybridAutomatic Repeat Request Round Trip Time, HARQ RTT, timer value that isgenerated as 7+l*N+s in which N is a Physical Uplink Control Channel,PUCCH, repetition factor, l is the quantity of the plurality of TBsidentified in the scheduling message and s is a delay factor thatprovides timer alignment corresponding to machine type communicationphysical downlink control channel, MPDCCH, operations.

Some embodiments provide that the scheduling message is a firstscheduling message, the multiple TBs include a first plurality of TB's,the quantity of TB's includes a first quantity of TBs, and theacknowledgement timer value includes a first acknowledgement timervalue. In such embodiments, the UE is further caused to receive a secondscheduling message that includes a second schedule identifying a secondplurality of TBs; determine a second quantity of TBs that are identifiedin the second scheduling message, and dynamically generate a secondacknowledgement timer value that corresponds to the second plurality ofTBs and that is different from the first acknowledgement timer value.

Some embodiments are directed to methods of operating a wireless devicein a communication network. Such methods may include receiving ascheduling message that includes a schedule identifying a plurality oftransmission blocks, TBs, determining a quantity of the plurality of TBsthat are identified in the scheduling message, determining a quantity ofHybrid Automatic Repeat Request Acknowledgement, HARQ ACKs in an ACKbundle identified in the scheduling message and dynamically generatingan acknowledgement timer value that corresponds to the quantity of theplurality of TBs and the quantity of HARQ ACKs in the ACK bundle.

In some embodiments, dynamically generating the acknowledgement timervalue comprises generating an acknowledgment timer value that is afunction of the quantity of the plurality of TBs and the quantity ofHARQ ACKs in the ACK bundle.

In some embodiments, the scheduling message comprises a downlink controlindication, DCI.

Some embodiments provide that dynamically generating the acknowledgementtimer value comprises multiplying a portion of a timer value by thequantity of the plurality of TBs in the scheduling message and by thequantity of HARQ ACKs in the ACK bundle identified in the schedulingmessage.

In some embodiments, the acknowledgement timer value comprises a HybridAutomatic Repeat Request Round Trip Time, HARQ RTT, timer value that isgenerated as 7+N*m in which N is a Physical Uplink Control Channel,PUCCH, repetition factor, and m is the number of HARQ ACK bundlesidentified in the scheduling message. In some embodiments, m isgenerated as l/i in which l is the quantity of the plurality of TBsidentified in the scheduling message and i is the quantity of HARQ ACKsper ACK bundle.

In some embodiments, the acknowledgement timer value comprises a HybridAutomatic Repeat Request Round Trip Time, HARQ RTT, timer value that isgenerated as 7+N*m+s in which N is a Physical Uplink Control Channel,PUCCH, repetition factor, m is the number of HARQ ACK bundles identifiedin the scheduling message and s is a delay factor that provides timeralignment corresponding to machine type communication physical downlinkcontrol channel, MPDCCH, operations. Some embodiments provide that m isgenerated as l/i in which l is the quantity of the plurality of TBsidentified in the scheduling message and i is the quantity of HARQ ACKsper ACK bundle.

In some embodiments, the scheduling message comprises a first schedulingmessage, the plurality of TBs comprises a first plurality of TB's,wherein the quantity of the plurality of TB's comprises a first quantityof TBs, the quantity of HARQ ACKs in the ACK bundle comprises a firstquantity of HARQ ACKs in the ACK bundle, and the acknowledgement timervalue comprises a first acknowledgement timer value. In suchembodiments, operations may further include receiving a secondscheduling message that includes a second schedule identifying a secondplurality of TBs, determining a second quantity of the plurality of TBsthat are identified in the second scheduling message, determining asecond quantity of HARQ ACKs in the bundle, and dynamically generating asecond acknowledgement timer value that corresponds to the secondplurality of TBs and the second quantity of HARQ ACKs in the ACK bundleand that is different from the first acknowledgement timer value.

Some embodiments are directed to methods of operating a radio accessnetwork node, RAN, in a communication network. Operations according tosuch methods include sending, to a UE, a scheduling message thatincludes a schedule identifying a plurality of transmission blocks, TBs,that causes the UE to determine a quantity of the plurality of TBs thatare identified in the scheduling message, and that causes the UE todetermine a quantity of HARQ ACKs in an ACK bundle identified in thescheduling message and to dynamically generate an acknowledgement timervalue that corresponds to the quantity of the plurality of TBs and thequantity of HARQ ACKs in the ACK bundle.

In some embodiments, the acknowledgement timer value is a function ofthe quantity of the plurality of transmission blocks and the quantity ofHARQ ACKs in the ACK bundle.

Some embodiments provide that the scheduling message comprises adownlink control indication, DCI.

In some embodiments, the acknowledgement timer value comprises a productfrom multiplying a portion of a timer value by the quantity of theplurality of TBs in the scheduling message and quantity of HARQ ACKs inthe ACK bundle.

In some embodiments, the acknowledgement timer value comprises a HybridAutomatic Repeat Request Round Trip Time, HARQ RTT, timer value that isgenerated as 7+N*m in which N is a Physical Uplink Control Channel,PUCCH, repetition factor, and m is the number of HARQ ACK bundlesidentified in the scheduling message. In some embodiments, m isgenerated as l/i in which l is the quantity of the plurality of TBsidentified in the scheduling message and i is the quantity of HARQ ACKsper ACK bundle.

Some embodiments provide that the acknowledgement timer value comprisesa Hybrid Automatic Repeat Request Round Trip Time, HARQ RTT, timer valuethat is generated as 7+N*m+s in which N is a Physical Uplink ControlChannel, PUCCH, repetition factor, m is the number of HARQ ACK bundlesidentified in the scheduling message, and s is a delay factor thatprovides timer alignment corresponding to machine type communicationphysical downlink control channel, MPDCCH, operations. Some embodimentsprovide that m is generated as l/i in which l is the quantity of theplurality of TBs identified in the scheduling message and i is thequantity of HARQ ACKs per ACK bundle.

In some embodiments, the scheduling message comprises a first schedulingmessage, the plurality of TBs comprises a first plurality of TB's, thequantity of the plurality of TB's comprises a first quantity of TB s,the quantity of HARQ ACKs in the ACK bundle comprises a first quantityof HARQ ACKs in the ACK bundle, and the acknowledgement timer valuecomprises a first acknowledgement timer value. Operations according tosuch embodiments further include receiving a second scheduling messagethat includes a second schedule identifying a second plurality of TBs,determining a second quantity of the plurality of TBs that areidentified in the second scheduling message, determining a secondquantity of HARQ ACKs in the ACK bundle, and dynamically generating asecond acknowledgement timer value that corresponds to the secondplurality of TBs and the second quantity of HARQ ACKs in the ACK bundleand that is different from the first acknowledgement timer value.

Some embodiments are directed to methods of operating a core network,CN, node (500) configured to operate in a communication network.Operations according to such methods include sending, to a UE, ascheduling message that includes a schedule identifying a plurality oftransmission blocks, TBs, that causes the UE to determine a quantity ofthe plurality of TBs that are identified in the scheduling message, andthat causes the UE to determine a quantity of HARQ ACKs in an ACK bundleidentified in the scheduling message and to dynamically generate anacknowledgement timer value that corresponds to the quantity of theplurality of TBs and the quantity of HARQ ACKs in the ACK bundle.

In some embodiments, the acknowledgement timer value is a function ofthe quantity of the plurality of transmission blocks and the quantity ofHARQ ACKs in the ACK bundle.

Some embodiments provide that the scheduling message comprises adownlink control indication, DCI.

In some embodiments, the acknowledgement timer value comprises a productfrom multiplying a portion of a timer value by the quantity of theplurality of TBs in the scheduling message and quantity of HARQ ACKs inthe ACK bundle.

Some embodiments provide that the acknowledgement timer value comprisesa Hybrid Automatic Repeat Request Round Trip Time, HARQ RTT, timer valuethat is generated as 7+N*m in which N is a Physical Uplink ControlChannel, PUCCH, repetition factor, and m is the number of HARQ ACKbundles identified in the scheduling message. In some embodiments, m isgenerated as l/i in which l is the quantity of the plurality of TBsidentified in the scheduling message and i is the quantity of HARQ ACKsper ACK bundle.

In some embodiments, the acknowledgement timer value comprises a HybridAutomatic Repeat Request Round Trip Time, HARQ RTT, timer value that isgenerated as 7+N*m+s in which N is a Physical Uplink Control Channel,PUCCH, repetition factor, m is the number of HARQ ACK bundles identifiedin the scheduling message, and s is a delay factor that provides timeralignment corresponding to machine type communication physical downlinkcontrol channel, MPDCCH, operations. Some embodiments provide that m isgenerated as l/i in which l is the quantity of the plurality of TBsidentified in the scheduling message and i is the quantity of HARQ ACKsper ACK bundle.

In some embodiments, the plurality of TBs comprises a first plurality ofTB's, the plurality of TBs comprises a first plurality of TB's, thequantity of the plurality of TB's comprises a first quantity of TBs, thequantity of HARQ ACKs in the ACK bundle comprises a first quantity ofHARQ ACKs in the ACK bundle, and the acknowledgement timer valuecomprises a first acknowledgement timer value. In such methods,operations may further include receiving a second scheduling messagethat includes a second schedule identifying a second plurality of TBs,determining a second quantity of the plurality of TBs that areidentified in the second scheduling message, determining a secondquantity of HARQ ACKs in the ACK bundle, and dynamically generating asecond acknowledgement timer value that corresponds to the secondplurality of TBs and the second quantity of HARQ ACKs in the ACK bundleand that is different from the first acknowledgement timer value.

In some embodiments, the communication network includes a narrow bandinternet of things network, NBIoT. Some embodiments provide that thecommunication network includes an enhanced Machine Type Communication,eMTC, network.

In some embodiments, a wireless device includes processing circuitry andmemory coupled with the processing circuitry. The memory includesinstructions that when executed by the processing circuitry causes thewireless device to perform operations disclosed herein.

Some embodiments are directed to a wireless device that is adapted toperform operations according to any methods disclosed herein.

Some embodiments are directed to a computer program comprising programcode to be executed by processing circuitry of a wireless device.Execution of the program code causes the wireless device to perform anyoperations disclosed herein.

Some embodiments are directed to a computer program product comprising anon-transitory storage medium including program code to be executed byprocessing circuitry of a wireless device. Execution of the program codecauses the wireless device to perform any operations disclosed herein.

According to embodiments disclosed herein, by dynamically generating anacknowledgement timer value based on the quantity of transmission blocksin a DCI, efficiencies in power consumption and/or performance may berealized.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the disclosure and are incorporated in and constitute apart of this application, illustrate certain non-limiting embodiments ofinventive concepts. In the drawings:

FIG. 1 illustrates a wireless communication system;

FIG. 2 is a block diagram illustrating a wireless device UE according tosome embodiments of inventive concepts;

FIG. 3 is a block diagram illustrating a radio access network RAN node(e.g., a base station eNB/gNB) according to some embodiments ofinventive concepts;

FIG. 4 is a block diagram illustrating a core network CN node (e.g., anAMY node, an SMF node, etc.) according to some embodiments of inventiveconcepts;

FIG. 5 is a flow chart illustrating operations of a wireless deviceaccording to some embodiments of inventive concepts;

FIG. 6 is a flow chart illustrating operations of a radio access networknode according to some embodiments of inventive concepts;

FIG. 7 is a flow chart illustrating operations of a core network nodeaccording to some embodiments of inventive concepts;

FIG. 8 is a flow chart illustrating operations of a wireless deviceaccording to some embodiments of inventive concepts;

FIG. 9 is a flow chart illustrating operations of a radio access networknode according to some embodiments of inventive concepts;

FIG. 10 is a flow chart illustrating operations of a core network nodeaccording to some embodiments of inventive concepts;

FIG. 11 is a block diagram of a wireless network in accordance with someembodiments;

FIG. 12 is a block diagram of a user equipment in accordance with someembodiments

FIG. 13 is a block diagram of a virtualization environment in accordancewith some embodiments;

FIG. 14 is a block diagram of a telecommunication network connected viaan intermediate network to a host computer in accordance with someembodiments;

FIG. 15 is a block diagram of a host computer communicating via a basestation with a user equipment over a partially wireless connection inaccordance with some embodiments;

FIG. 16 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipment inaccordance with some embodiments;

FIG. 17 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipment inaccordance with some embodiments;

FIG. 18 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipment inaccordance with some embodiments; and

FIG. 19 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipment inaccordance with some embodiments.

DETAILED DESCRIPTION

Inventive concepts will now be described more fully hereinafter withreference to the accompanying drawings, in which examples of embodimentsof inventive concepts are shown. Inventive concepts may, however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein. Rather, these embodiments areprovided so that this disclosure will be thorough and complete, and willfully convey the scope of present inventive concepts to those skilled inthe art. It should also be noted that these embodiments are not mutuallyexclusive. Components from one embodiment may be tacitly assumed to bepresent/used in another embodiment.

The following description presents various embodiments of the disclosedsubject matter. These embodiments are presented as teaching examples andare not to be construed as limiting the scope of the disclosed subjectmatter. For example, certain details of the described embodiments may bemodified, omitted, or expanded upon without departing from the scope ofthe described subject matter.

As provided herein, the UE (eMTC) may listen for (UL grants) forretransmissions in case of multiple scheduled TBs. In some embodiments,the UE may listen on the machine type communication physical downlinkcontrol channel, MPDCCH. In some embodiments, for asynchronous adaptiveHARQ, HARQ feedback signal is not sent, except for BL UEs and UEs inenhanced coverage. The UE may follow what the PDCCH, MPDCCH and/orSPDCCH asks the UE to do. Examples include performing a transmission ora retransmission, among others. For BL UEs or UEs in enhanced coverage,a downlink ACK response to uplink (re)transmissions may be sent in theDCI with C-RNTI or SPS C-RNTI scheduling MPDCCH.

FIG. 2 is a block diagram illustrating elements of a wireless device 300(also referred to as a mobile terminal, a mobile communication terminal,a wireless communication device, a wireless terminal, mobile device, awireless communication terminal, user equipment, UE, a user equipmentnode/terminal/device, etc.) configured to provide wireless communicationaccording to embodiments of inventive concepts. As shown, the UE mayinclude an antenna 307, and transceiver circuitry 301 (also referred toas a transceiver) including a transmitter and a receiver configured toprovide uplink and downlink radio communications with a base station(s)(e.g., also referred to as a RAN node) of a radio access network.Wireless device UE may also include processing circuitry 303 (alsoreferred to as a processor) coupled to the transceiver circuitry, andmemory circuitry 305 (also referred to as memory) coupled to theprocessing circuitry. The memory circuitry 305 may include computerreadable program code that when executed by the processing circuitry 303causes the processing circuitry to perform operations according toembodiments disclosed herein. According to other embodiments, processingcircuitry 303 may be defined to include memory so that separate memorycircuitry is not required. Wireless device UE may also include aninterface (such as a user interface) coupled with processing circuitry303, and/or wireless device UE may be incorporated in a vehicle.

As discussed herein, operations of wireless device UE may be performedby processing circuitry 303 and/or transceiver circuitry 301. Forexample, processing circuitry 303 may control transceiver circuitry 301to transmit communications through transceiver circuitry 301 over aradio interface to a radio access network, RAN, node, (also referred toas a base station) and/or to receive communications through transceivercircuitry 301 from a RAN node over a radio interface. Moreover, modulesmay be stored in memory circuitry 305, and these modules may provideinstructions so that when instructions of a module are executed byprocessing circuitry 303, processing circuitry 303 performs respectiveoperations (e.g., operations discussed below with respect to ExampleEmbodiments relating to wireless devices).

FIG. 3 is a block diagram illustrating elements of a RAN node 400 (alsoreferred to as a network node, base station, eNodeB/eNB, gNodeB/gNB,etc.) of a RAN configured to provide cellular communication according toembodiments of inventive concepts. RAN node 400 may be provided, forexample, as discussed below. As shown, the RAN node may includetransceiver circuitry 401 (also referred to as a transceiver) includinga transmitter and a receiver configured to provide uplink and downlinkradio communications with mobile terminals. The RAN node may includenetwork interface circuitry 407 (also referred to as a network interface11) configured to provide communications with other nodes (e.g., withother base stations) of the RAN and/or core network, CN. The networknode may also include processing circuitry 403 (also referred to as aprocessor) coupled to the transceiver circuitry, and memory circuitry405 (also referred to as memory) coupled to the processing circuitry.The memory circuitry 405 may include computer readable program code thatwhen executed by the processing circuitry 403 causes the processingcircuitry to perform operations according to embodiments disclosedherein. According to other embodiments, processing circuitry 403 may bedefined to include memory so that a separate memory circuitry is notrequired.

As discussed herein, operations of the RAN node may be performed byprocessing circuitry 403, network interface 407, and/or transceiver 401.For example, processing circuitry 403 may control transceiver 401 totransmit downlink communications through transceiver 401 over a radiointerface to one or more mobile terminals UEs and/or to receive uplinkcommunications through transceiver 401 from one or more mobile terminalsUEs over a radio interface. Similarly, processing circuitry 403 maycontrol network interface 407 to transmit communications through networkinterface 407 to one or more other network nodes and/or to receivecommunications through network interface from one or more other networknodes. Moreover, modules may be stored in memory 405, and these modulesmay provide instructions so that when instructions of a module areexecuted by processing circuitry 403, processing circuitry 403 performsrespective operations (e.g., operations discussed below with respect toExample Embodiments relating to RAN nodes).

According to some other embodiments, a network node may be implementedas a CN node without a transceiver. In such embodiments, transmission toa wireless device UE may be initiated by the network node so thattransmission to the wireless device is provided through a network nodeincluding a transceiver (e.g., through a base station or RAN node).According to embodiments where the network node is a RAN node includinga transceiver, initiating transmission may include transmitting throughthe transceiver.

FIG. 4 is a block diagram illustrating elements of a CN node (e.g., anSMF node, an AMF node, etc.) of a communication network configured toprovide cellular communication according to embodiments of inventiveconcepts. As shown, the CN node may include network interface circuitry507 (also referred to as a network interface) configured to providecommunications with other nodes of the core network and/or the radioaccess network RAN. The CN node may also include a processing circuitry503 (also referred to as a processor) coupled to the network interfacecircuitry, and memory circuitry 505 (also referred to as memory) coupledto the processing circuitry. The memory circuitry 505 may includecomputer readable program code that when executed by the processingcircuitry 503 causes the processing circuitry to perform operationsaccording to embodiments disclosed herein. According to otherembodiments, processing circuitry 503 may be defined to include memoryso that a separate memory circuitry is not required.

As discussed herein, operations of the CN node may be performed byprocessing circuitry 503 and/or network interface circuitry 507. Forexample, processing circuitry 503 may control network interfacecircuitry 507 to transmit communications through network interfacecircuitry 507 to one or more other network nodes and/or to receivecommunications through network interface circuitry from one or moreother network nodes. Moreover, modules may be stored in memory 505, andthese modules may provide instructions so that when instructions of amodule are executed by processing circuitry 503, processing circuitry503 performs respective operations (e.g., operations discussed belowwith respect to Example Embodiments relating to core network nodes).

When the feature of scheduling multiple TBs with one DCI is used,varying number of TBs may be scheduled with each DCI. For example, insome embodiments, the maximum amount of TBs scheduled with a single DCIcan be 8 TBs both in uplink and downlink for CE Mode A, and 4 TBs bothin uplink and downlink for CE Mode B.

Some embodiments may configure a HARQ RTT timer according to the maximumnumber of scheduled TBs. However, successive DCIs may schedule differentamounts of TBs. For example, a first DCI may schedule 8 TBs and thefollowing DCI may schedule 4 TBs. Thus, static value for HARQ RTT Timermay be limiting as it may either be too long for the 4 TBs if configuredaccording to the maximum value (8). This may result in the UE wastingtime and power while idle for the remaining duration of the timer. Insome embodiments, the timer may need to be reconfigured for every DCIseparately, which may waste UE power and resources as the UE may need tobe reconfigured frequently. As used herein, the term downlink controlindication, DCI, may also include, comprise and/or be usedinterchangeably with the term downlink control information, which is aterm that is well known to those having skill in the relevant field.

According to some embodiments, HARQ RTT timers may be extendeddynamically by multiplying at least a portion of the timer value by thenumber of scheduled TBs by one DCI. According to such embodiments, theUE may dynamically adapt to the varying number of scheduled TBs byadjusting the HARQ RTT timer dynamically.

When scheduling multiple TBs with one DCI, a varying number of TBs maybe scheduled with each DCI.

According to some embodiments herein, the UE may apply a multiplier(e.g., denoted as l) to at least a portion of the (UL) HARQ RTT timer.In some embodiments, this multiplier, may be equivalent to the number ofTBs scheduled by the latest DCI. In some embodiments, the information toUE MAC layer, where the timer is started and used, may be defined in thelower layers according to the information conveyed in the DCI. In thismanner, the UE may be able to dynamically adjust the HARQ RTT timeraccording to the number of TBs scheduled by each DCI.

In some embodiments, a different mechanism may be used depending onwhether the UE is full-duplex (FD) or half-duplex (HD) FDD UE. For FD,it may be possible to start monitoring earlier and the legacy timervalues may be sufficient. For HD, an extension of the monitoringaccording to the multiplier 1 may be specified. Some embodiments providethat whether UE should follow FD of HD behavior may be indicated in theDCI, and/or the eNB and UE may act according to the UE capability. Forexample, the approach may be determined based on whether the UE is FD orHD.

Some embodiments provide that for BL UEs and UEs in enhanced coverage,HARQ RTT Timer may correspond to 7+N where N is the used PUCCHrepetition factor, where only valid (configured) UL subframes asconfigured by upper layers in fdd-UplinkSubframeBitmapBR are counted. Incase of TDD, HARQ RTT Timer may correspond to 3+k+N, where k is theinterval between the last repetition of downlink transmission and thefirst repetition of the transmission of associated HARQ feedback, and Nis the used PUCCH repetition factor, where only valid UL subframes arecounted.

In some embodiments, the UE may apply the multiplier 1 to the HARQ RTTTimer value. For BL UEs and UEs in enhanced coverage, when the featureof scheduling multiple TBs with a single DCI is used, HARQ RTT Timer maybe dynamically adjusted as a function of the number of TBs scheduled ina given DCI. For example, the HARQ RTT Timer value may be determined as7+l*N where N is the PUCCH repetition factor, where only valid(configured) UL subframes as configured by upper layers infdd-UplinkSubframeBitmapBR are counted, and where l is the number of TBsscheduled by the corresponding DCI.

Some embodiments provide that for BL UEs and UEs in enhanced coverage,when multiple TBs are scheduled by PDCCH and HARQ-ACK bundling isconfigured, the HARQ RTT Timer corresponds to 7+k*N where N is the usedPUCCH repetition factor and k is the number of HARQ feedback bundles,k=ceiling(N_(TB)/M), where N_(TB) is the number of scheduled TBs asindicated in PDCCH and M is the Multi-TB HARQ-ACK bundling sizeindicated in the corresponding PDCCH. In some embodiments, only valid(configured) UL subframes as configured by upper layers infdd-UplinkSubframeBitmapBR are counted.

In some embodiments, the scheduling delay (i.e. 7 above) may be adjustedaccording to the delay from UE and eNB processing times. For example,the scheduling delay may be increased if more processing time is neededor reduced if less time is sufficient. Some embodiments provide that afixed value may be captured in specifications.

In some embodiments, additional delay s on top of 7+l*N may be accountedfor if needed for alignment with future MPDCCH opportunities. Forexample, the total timer length may be 7+l*N+s.

Operations of the wireless device 300 (implemented using the structureof the block diagram of FIG. 2 ) will now be discussed with reference tothe flow chart of FIG. 5 according to some embodiments of inventiveconcepts. For example, modules may be stored in memory 305 of FIG. 2 ,and these modules may provide instructions so that when the instructionsof a module are executed by respective wireless device processingcircuitry 303, processing circuitry 303 performs respective operationsof the flow chart. Methods according to some embodiments includereceiving (510) a scheduling message that includes a scheduleidentifying multiple TBs. Operations include determining (520) aquantity of the TBs that are identified in the scheduling message anddynamically generating (530) an acknowledgement timer value thatcorresponds to the quantity of the plurality of TBs.

In some embodiments, dynamically generating the acknowledgement timervalue includes generating an acknowledgment timer value that is afunction of the quantity of the TBs. Some embodiments provide that thescheduling message includes a downlink control indication, DCI. In someembodiments, dynamically generating the acknowledgement timer valueincludes multiplying a portion of a timer value by the quantity of theTBs in the scheduling message.

In some embodiments, the acknowledgement timer value includes a HybridAutomatic Repeat Request Round Trip Time, HARQ RTT, timer value that isgenerated as 7+l*N in which N is a Physical Uplink Control Channel,PUCCH, repetition factor and l is the quantity of the TBs identified inthe scheduling message.

Some embodiments provide that the acknowledgement timer value includes aHybrid Automatic Repeat Request Round Trip Time, HARQ RTT, timer valuethat is generated as 7+l*N+s in which N is a Physical Uplink ControlChannel, PUCCH, repetition factor, l is the quantity of the plurality ofTBs identified in the scheduling message and s is a delay factor thatprovides timer alignment corresponding to machine type communicationphysical downlink control channel, MPDCCH, operations.

Some embodiments provide that the scheduling message includes a firstscheduling message, the TBs comprises first TB's, the quantity of theTB's is a first quantity of TBs, and the acknowledgement timer value isa first acknowledgement timer value. Since the acknowledgement timervalue may be determined dynamically here, another scheduling messagewith a different number of TBs scheduled therein may cause a differentacknowledgement timer value to be generated.

In some embodiments, the communication network includes a narrow bandinternet of things network, NBIoT.

Some embodiments provide that the communication network includes anenhanced Machine Type Communication, eMTC, network.

Operations of a RAN node 400 (implemented using the structure of FIG. 3) will now be discussed with reference to the flow chart of FIG. 6according to some embodiments of inventive concepts. For example,modules may be stored in memory 405 of FIG. 3 , and these modules mayprovide instructions so that when the instructions of a module areexecuted by respective RAN node processing circuitry 403, processingcircuitry 403 performs respective operations of the flow chart.

According to some embodiments, operations may include sending 610, to aUE, a scheduling message that includes a schedule identifying multipleTBs and that causes the UE to determine a quantity of the TBs that areidentified in the scheduling message and to dynamically generate anacknowledgement timer value that corresponds to the quantity of the TBs.

Network CN node 500 (implemented using the structure of FIG. 4 ) willnow be discussed with reference to the flow chart of FIG. 7 according tosome embodiments of inventive concepts. For example, modules may bestored in memory 505 of FIG. 4 , and these modules may provideinstructions so that when the instructions of a module are executed byrespective CN node processing circuitry 503, processing circuitry 503performs respective operations of the flow chart.

According to some embodiments, operations may include sending 710, to aUE, a scheduling message that includes a schedule identifying multipleTBs and that causes the UE to determine a quantity of the TBs that areidentified in the scheduling message and to dynamically generate anacknowledgement timer value that corresponds to the quantity of the TBs.

In some embodiments, the UE may dynamically adapt to a varying number ofscheduled TBs by adjusting the HARQ RTT timer dynamically for the casein which the HARQ ACKs are bundled.

As used herein, the bundling of ACKs/NACKs implies that the outcome ofthe decoding of downlink transport blocks from multiple downlinksubframes can be come into a single HARQ feedback transmitted in theuplink.

Some embodiments provide that bundled HARQ ACKs are supported bymultiple TB scheduling. In some embodiments, a multiplier may beincluded in as part of the HARQ RTT timer to account for the number ofbundled HARQ ACKs sent. For example, the HARQ RTT timer value may bedetermined as 7+m*N in which the multiplier “m” equals the number ofHARQ ACK bundles. Some embodiments provide that the number of HARQ ACKbundles depends on the number of TBs scheduled and the configurationgiven in the DCI, which indicates how many ACKs are included in a singlebundle.

Thus, m=ceil(l/i), where “l” equals the number of TBs scheduled and “i”equals the number of ACKs included in one bundle, as indicated by theDCI. Some embodiments provide that “i” may be a value of 1, 2, 3, or 4,however such embodiments are non-limiting as “i” may be a differentnumber.

According to embodiments herein, a technical solution provides adynamically adaptive multiplier to adjust the HARQ RTT timer lengthaccording to the number of TBs scheduled by a single DCI and the numberof HARQ ACKs to be sent.

Operations of the wireless device 300 (implemented using the structureof the block diagram of FIG. 2 ) will now be discussed with reference tothe flow chart of FIG. 8 according to some embodiments of inventiveconcepts. For example, modules may be stored in memory 305 of FIG. 2 ,and these modules may provide instructions so that when the instructionsof a module are executed by respective wireless device processingcircuitry 303, processing circuitry 303 performs respective operationsof the flow chart. Methods according to some embodiments includereceiving (810) a scheduling message that includes a scheduleidentifying multiple TBs. Operations include determining (820) aquantity of the TBs that are identified in the scheduling message,determining (825) a quantity of HARQ ACK bundles that are identified inthe scheduling message, and dynamically generating (830) anacknowledgement timer value that corresponds to the quantity of theplurality of TBs and the quantity of HARQ ACK bundles.

In some embodiments, dynamically generating the acknowledgement timervalue includes generating an acknowledgment timer value that is afunction of the quantity of the TBs and the quantity of HARQ ACKbundles. Some embodiments provide that the scheduling message includes adownlink control indication, DCI. In some embodiments, dynamicallygenerating the acknowledgement timer value includes multiplying aportion of a timer value by the quantity of the TBs in the schedulingmessage and the quantity of HARQ ACK bundles in the scheduling message.

In some embodiments, the acknowledgement timer value includes a HybridAutomatic Repeat Request Round Trip Time, HARQ RTT, timer value that isgenerated as 7+N*m in which N is a Physical Uplink Control Channel,PUCCH, repetition factor, l is the quantity of the TBs identified in thescheduling message and m is the number of HARQ ACK bundles identified inthe scheduling message.

Some embodiments provide that the acknowledgement timer value includes aHybrid Automatic Repeat Request Round Trip Time, HARQ RTT, timer valuethat is generated as 7+N*m+s in which N is a Physical Uplink ControlChannel, PUCCH, repetition factor, l is the quantity of the plurality ofTBs identified in the scheduling message, m is the number of HARQ ACKbundles identified in the scheduling message and s is a delay factorthat provides timer alignment corresponding to machine typecommunication physical downlink control channel, MPDCCH, operations.

Some embodiments provide that the scheduling message includes a firstscheduling message, the TBs comprises first TB's, the quantity of theTB's is a first quantity of TBs, the quantity of HARQ ACK bundles is afirst quantity of HARQ ACK bundles, and the acknowledgement timer valueis a first acknowledgement timer value. Since the acknowledgement timervalue may be determined dynamically here, another scheduling messagewith a different number of TBs scheduled and/or a different quantity ofHARQ ACK bundles may cause a different acknowledgement timer value to begenerated.

In some embodiments, the communication network includes a narrow bandinternet of things network, NBIoT.

Some embodiments provide that the communication network includes anenhanced Machine Type Communication, eMTC, network.

Operations of a RAN node 400 (implemented using the structure of FIG. 3) will now be discussed with reference to the flow chart of FIG. 9according to some embodiments of inventive concepts. For example,modules may be stored in memory 405 of FIG. 3 , and these modules mayprovide instructions so that when the instructions of a module areexecuted by respective RAN node processing circuitry 403, processingcircuitry 403 performs respective operations of the flow chart.

According to some embodiments, operations may include sending 910, to aUE, sending, to a UE, a scheduling message that includes a scheduleidentifying a plurality of transmission blocks, TBs, that causes the UEto determine a quantity of the plurality of TBs that are identified inthe scheduling message, and that causes the UE to determine the quantityof HARQ ACK bundles and to dynamically generate an acknowledgement timervalue that corresponds to the quantity of the plurality of TBs and thequantity of HARQ ACK bundles.

Network CN node 500 (implemented using the structure of FIG. 4 ) willnow be discussed with reference to the flow chart of FIG. 10 accordingto some embodiments of inventive concepts. For example, modules may bestored in memory 505 of FIG. 4 , and these modules may provideinstructions so that when the instructions of a module are executed byrespective CN node processing circuitry 503, processing circuitry 503performs respective operations of the flow chart.

According to some embodiments, operations may include sending 1010, to aUE, a scheduling message that includes a schedule identifying aplurality of transmission blocks, TBs, that causes the UE to determine aquantity of the plurality of TBs that are identified in the schedulingmessage, and that causes the UE to determine the quantity of HARQ ACKbundles and to dynamically generate an acknowledgement timer value thatcorresponds to the quantity of the plurality of TBs and the quantity ofHARQ ACK bundles.

As used herein, the term downlink control indication may also include,comprise and/or be used interchangeably with the term downlink controlinformation, which is a term that is well known to those having skill inthe relevant field.

Example embodiments are discussed below.

1. A method of operating a wireless device in a communication network,the method comprising:

receiving a scheduling message that includes a schedule identifying aplurality of transmission blocks, TBs;

determining a quantity of the plurality of TBs that are identified inthe scheduling message; and

dynamically generating an acknowledgement timer value that correspondsto the quantity of the plurality of TBs.

2. The method of embodiment 1, wherein dynamically generating theacknowledgement timer value comprises generating an acknowledgment timervalue that is a function of the quantity of the plurality oftransmission blocks.

3. The method of any of embodiments 1 and 2, wherein the schedulingmessage comprises a downlink control indication, DCI.

4. The method of any of embodiments 1-3, wherein dynamically generatingthe acknowledgement timer value comprises multiplying a portion of atimer value by the quantity of the plurality of TBs in the schedulingmessage.

5. The method of any of embodiments 1-4, wherein the acknowledgementtimer value comprises a Hybrid Automatic Repeat Request Round Trip Time,HARQ RTT, timer value that is generated as 7+l*N in which N is aPhysical Uplink Control Channel, PUCCH, repetition factor and l is thequantity of the plurality of TBs identified in the scheduling message.

6. The method of any of embodiments 1-5, wherein the acknowledgementtimer value comprises a Hybrid Automatic Repeat Request Round Trip Time,HARQ RTT, timer value that is generated as 7+l*N+s in which N is aPhysical Uplink Control Channel, PUCCH, repetition factor, l is thequantity of the plurality of TBs identified in the scheduling messageand s is a delay factor that provides timer alignment corresponding tomachine type communication physical downlink control channel, MPDCCH,operations.

7. The method of any of embodiments 1-6, wherein the scheduling messagecomprises a first scheduling message,

wherein the plurality of TBs comprises a first plurality of TB's,

wherein the quantity of the plurality of TB's comprises a first quantityof TBs, and

wherein the acknowledgement timer value comprises a firstacknowledgement timer value,

the method further comprising:

receiving a second scheduling message that includes a second scheduleidentifying a second plurality of TBs;

determining a second quantity of the plurality of TBs that areidentified in the second scheduling message; and

dynamically generating a second acknowledgement timer value thatcorresponds to the second plurality of TBs and that is different fromthe first acknowledgement timer value.

8. The method of any of embodiments 1-7, wherein the communicationnetwork comprises a narrow band internet of things network, NBIoT.

9. The method of any of embodiments 1-7, wherein the communicationnetwork comprises an enhanced Machine Type Communication, eMTC, network.

10. A wireless device comprising:

processing circuitry; and

memory coupled with the processing circuitry, wherein the memoryincludes instructions that when executed by the processing circuitrycauses the wireless device to perform operations according to any ofEmbodiments 1-9.

12. A wireless device adapted to perform according to any of Embodiments1-9.

13. A computer program comprising program code to be executed byprocessing circuitry of a wireless device, whereby execution of theprogram code causes the wireless device to perform operations accordingto any of embodiments 1-9.

14. A computer program product comprising a non-transitory storagemedium including program code to be executed by processing circuitry ofa wireless device, whereby execution of the program code causes thewireless device to perform operations according to any of embodiments1-9.

15. A method of operating a radio access network node, RAN, in acommunication network, the method comprising:

sending, to a UE, a scheduling message that includes a scheduleidentifying a plurality of transmission blocks, TBs, and that causes theUE to determine a quantity of the plurality of TBs that are identifiedin the scheduling message and to dynamically generate an acknowledgementtimer value that corresponds to the quantity of the plurality of TBs.

16. The method of embodiment 15, wherein the acknowledgement timer valueis a function of the quantity of the plurality of transmission blocks.

17. The method of any of embodiments 15 and 16, wherein the schedulingmessage comprises a downlink control indication, DCI.

18. The method of any of embodiments 15-17, wherein the acknowledgementtimer value comprises a product from multiplying a portion of a timervalue by the quantity of the plurality of TBs in the scheduling message.

19. The method of any of embodiments 15-18, wherein the acknowledgementtimer value comprises a Hybrid Automatic Repeat Request Round Trip Time,HARQ RTT, timer value that is generated as 7+l*N in which N is aPhysical Uplink Control Channel, PUCCH, repetition factor and l is thequantity of the plurality of TBs identified in the scheduling message.

20. The method of any of embodiments 15-19, wherein the acknowledgementtimer value comprises a Hybrid Automatic Repeat Request Round Trip Time,HARQ RTT, timer value that is generated as 7+l*N+s in which N is aPhysical Uplink Control Channel, PUCCH, repetition factor, l is thequantity of the plurality of TBs identified in the scheduling messageand s is a delay factor that provides timer alignment corresponding tomachine type communication physical downlink control channel, MPDCCH,operations.

21. The method of any of embodiments 15-20, wherein the schedulingmessage comprises a first scheduling message,

wherein the plurality of TBs comprises a first plurality of TB's,

wherein the quantity of the plurality of TB's comprises a first quantityof TBs, and

wherein the acknowledgement timer value comprises a firstacknowledgement timer value,

wherein the UE is further caused to:

receive a second scheduling message that includes a second scheduleidentifying a second plurality of TBs;

determine a second quantity of the plurality of TBs that are identifiedin the second scheduling message; and

dynamically generate a second acknowledgement timer value thatcorresponds to the second plurality of TBs and that is different fromthe first acknowledgement timer value.

22. The method of any of embodiments 15-21, wherein the communicationnetwork comprises a narrow band internet of things network, NBIoT.

23. The method of any of embodiments 15-21, wherein the communicationnetwork comprises an enhanced Machine Type Communication, eMTC, network.

24. A radio access network, RAN, node comprising:

processing circuitry; and

memory coupled with the processing circuitry, wherein the memoryincludes instructions that when executed by the processing circuitrycauses the RAN node to perform operations according to any ofEmbodiments 15-23.

25. A radio access network, RAN, node adapted to perform according toany of Embodiments 15-23.

26. A computer program comprising program code to be executed byprocessing circuitry of a radio access network, RAN, node, wherebyexecution of the program code causes the RAN node to perform operationsaccording to any of embodiments 15-23.

27. A computer program product comprising a non-transitory storagemedium including program code to be executed by processing circuitry ofa radio access network, RAN, node, whereby execution of the program codecauses the RAN node to perform operations according to any ofembodiments 15-23.

28. A method of operating a core network, CN, node configured to operatein a communication network, the method comprising:

sending, to a UE, a scheduling message that includes a scheduleidentifying a plurality of transmission blocks, TBs, and causes the UEto determine a quantity of the plurality of TBs that are identified inthe scheduling message and to dynamically generate an acknowledgementtimer value that corresponds to the quantity of the plurality of TBs.

29. The method of embodiment 28, wherein the acknowledgement timer valueis a function of the quantity of the plurality of transmission blocks.

30. The method of any of embodiments 28 and 29, wherein the schedulingmessage comprises a downlink control indication, DCI.

31. The method of any of embodiments 28-30, wherein the acknowledgementtimer value comprises a product from multiplying a portion of a timervalue by the quantity of the plurality of TBs in the scheduling message.

32. The method of any of embodiments 28-31, wherein the acknowledgementtimer value comprises a Hybrid Automatic Repeat Request Round Trip Time,HARQ RTT, timer value that is generated as 7+l*N in which N is aPhysical Uplink Control Channel, PUCCH, repetition factor and l is thequantity of the plurality of TBs identified in the scheduling message.

33. The method of any of embodiments 28-32, wherein the acknowledgementtimer value comprises a Hybrid Automatic Repeat Request Round Trip Time,HARQ RTT, timer value that is generated as 7+l*N+s in which N is aPhysical Uplink Control Channel, PUCCH, repetition factor, l is thequantity of the plurality of TBs identified in the scheduling messageand s is a delay factor that provides timer alignment corresponding tomachine type communication physical downlink control channel, MPDCCH,operations.

34. The method of any of embodiments 28-33, wherein the schedulingmessage comprises a first scheduling message,

wherein the plurality of TBs comprises a first plurality of TB's,

wherein the quantity of the plurality of TB's comprises a first quantityof TBs, and

wherein the acknowledgement timer value comprises a firstacknowledgement timer value

the method further comprising:

receiving a second scheduling message that includes a second scheduleidentifying a second plurality of TBs;

determining a second quantity of the plurality of TBs that areidentified in the second scheduling message; and

dynamically generating a second acknowledgement timer value thatcorresponds to the second plurality of TBs and that is different fromthe first acknowledgement timer value.

35. The method of any of embodiments 28-34, wherein the communicationnetwork comprises a narrow band internet of things network, NBIoT.

36. The method of any of embodiments 28-35, wherein the communicationnetwork comprises an enhanced Machine Type Communication, eMTC, network.

37. A core network, CN, node comprising:

processing circuitry; and

memory coupled with the processing circuitry, wherein the memoryincludes instructions that when executed by the processing circuitrycauses the CN node to perform operations according to any of Embodiments28-36.

38. A core network, CN, node adapted to perform according to any ofEmbodiments 28-36.

39. A computer program comprising program code to be executed byprocessing circuitry of a core network, CN, node, whereby execution ofthe program code causes the CN node to perform operations according toany of embodiments 28-36.

40. A computer program product comprising a non-transitory storagemedium including program code to be executed by processing circuitry ofa core network, CN, node, whereby execution of the program code causesthe CN node to perform operations according to any of embodiments 28-36.

41. A method of operating a wireless device in a communication network,the method comprising:

receiving a scheduling message that includes a schedule identifying aplurality of transmission blocks, TBs;

determining a quantity of the plurality of TBs that are identified inthe scheduling message;

determining a quantity of Hybrid Automatic Repeat RequestAcknowledgement, HARQ ACKs in an ACK bundle identified in the schedulingmessage; and

dynamically generating an acknowledgement timer value that correspondsto the quantity of the plurality of TBs and the quantity of HARQ ACKs inthe ACK bundle.

42. The method of embodiment 41, wherein dynamically generating theacknowledgement timer value comprises generating an acknowledgment timervalue that is a function of the quantity of the plurality of TBs and thequantity of HARQ ACKs in the ACK bundle.

43. The method of any of embodiments 41 and 42, wherein the schedulingmessage comprises a downlink control indication, DCI.

44. The method of any of embodiments 41-43, wherein dynamicallygenerating the acknowledgement timer value comprises multiplying aportion of a timer value by the quantity of the plurality of TBs in thescheduling message and by the quantity of HARQ ACKs in the ACK bundleidentified in the scheduling message.

45. The method of any of embodiments 41-44, wherein the acknowledgementtimer value comprises a Hybrid Automatic Repeat Request Round Trip Time,HARQ RTT, timer value that is generated as 7+N*m in which N is aPhysical Uplink Control Channel, PUCCH, repetition factor, and m is thenumber of HARQ ACK bundles identified in the scheduling message, and

wherein m is generated as l/i in which l is the quantity of theplurality of TBs identified in the scheduling message and i is thequantity of HARQ ACKs per ACK bundle.

46. The method of any of embodiments 41-45, wherein the acknowledgementtimer value comprises a Hybrid Automatic Repeat Request Round Trip Time,HARQ RTT, timer value that is generated as 7+N*m+s in which N is aPhysical Uplink Control Channel, PUCCH, repetition factor, m is thenumber of HARQ ACK bundles identified in the scheduling message and s isa delay factor that provides timer alignment corresponding to machinetype communication physical downlink control channel, MPDCCH,operations, and

wherein m is generated as l/i in which l is the quantity of theplurality of TBs identified in the scheduling message and i is thequantity of HARQ ACKs per ACK bundle.

47. The method of any of embodiments 41-46, wherein the schedulingmessage comprises a first scheduling message,

wherein the plurality of TBs comprises a first plurality of TB's,

wherein the quantity of the plurality of TB's comprises a first quantityof TBs,

wherein the quantity of HARQ ACKs in the ACK bundle comprises a firstquantity of HARQ ACKs in the ACK bundle, and

wherein the acknowledgement timer value comprises a firstacknowledgement timer value,

the method further comprising:

receiving a second scheduling message that includes a second scheduleidentifying a second plurality of TBs;

determining a second quantity of the plurality of TBs that areidentified in the second scheduling message;

determining a second quantity of HARQ ACKs in the bundle, and

dynamically generating a second acknowledgement timer value thatcorresponds to the second plurality of TBs and the second quantity ofHARQ ACKs in the ACK bundle and that is different from the firstacknowledgement timer value.

48. The method of any of embodiments 41-47, wherein the communicationnetwork comprises a narrow band internet of things network, NBIoT.

49. The method of any of embodiments 41-47, wherein the communicationnetwork comprises an enhanced Machine Type Communication, eMTC, network.

50. A wireless device comprising:

processing circuitry; and

memory coupled with the processing circuitry, wherein the memoryincludes instructions that when executed by the processing circuitrycauses the wireless device to perform operations according to any ofEmbodiments 41-49.

51. A wireless device adapted to perform according to any of Embodiments41-49.

52. A computer program comprising program code to be executed byprocessing circuitry of a wireless device, whereby execution of theprogram code causes the wireless device to perform operations accordingto any of embodiments 41-49.

53. A computer program product comprising a non-transitory storagemedium including program code to be executed by processing circuitry ofa wireless device, whereby execution of the program code causes thewireless device to perform operations according to any of embodiments41-49.

54. A method of operating a radio access network node, RAN, in acommunication network, the method comprising:

sending, to a UE, a scheduling message that includes a scheduleidentifying a plurality of transmission blocks, TBs, that causes the UEto determine a quantity of the plurality of TBs that are identified inthe scheduling message, and that causes the UE to determine a quantityof HARQ ACKs in an ACK bundle identified in the scheduling message andto dynamically generate an acknowledgement timer value that correspondsto the quantity of the plurality of TBs and the quantity of HARQ ACKs inthe ACK bundle.

55. The method of embodiment 54, wherein the acknowledgement timer valueis a function of the quantity of the plurality of transmission blocksand the quantity of HARQ ACKs in the ACK bundle.

56. The method of any of embodiments 54 and 55, wherein the schedulingmessage comprises a downlink control indication, DCI.

57. The method of any of embodiments 54-56, wherein the acknowledgementtimer value comprises a product from multiplying a portion of a timervalue by the quantity of the plurality of TBs in the scheduling messageand quantity of HARQ ACKs in the ACK bundle.

58. The method of any of embodiments 54-57, wherein the acknowledgementtimer value comprises a Hybrid Automatic Repeat Request Round Trip Time,HARQ RTT, timer value that is generated as 7+N*m in which N is aPhysical Uplink Control Channel, PUCCH, repetition factor, and m is thenumber of HARQ ACK bundles identified in the scheduling message, and

wherein m is generated as l/i in which l is the quantity of theplurality of TBs identified in the scheduling message and i is thequantity of HARQ ACKs per ACK bundle.

59. The method of any of embodiments 54-58, wherein the acknowledgementtimer value comprises a Hybrid Automatic Repeat Request Round Trip Time,HARQ RTT, timer value that is generated as 7+N*m+s in which N is aPhysical Uplink Control Channel, PUCCH, repetition factor, m is thenumber of HARQ ACK bundles identified in the scheduling message, and sis a delay factor that provides timer alignment corresponding to machinetype communication physical downlink control channel, MPDCCH,operations, and

wherein m is generated as l/i in which l is the quantity of theplurality of TBs identified in the scheduling message and i is thequantity of HARQ ACKs per ACK bundle.

60. The method of any of embodiments 54-59, wherein the schedulingmessage comprises a first scheduling message,

wherein the plurality of TBs comprises a first plurality of TB's,

wherein the quantity of the plurality of TB's comprises a first quantityof TBs,

wherein the quantity of HARQ ACKs in the ACK bundle comprises a firstquantity of HARQ ACKs in the ACK bundle, and

wherein the acknowledgement timer value comprises a firstacknowledgement timer value,

the method further comprising:

receiving a second scheduling message that includes a second scheduleidentifying a second plurality of TBs;

determining a second quantity of the plurality of TBs that areidentified in the second scheduling message;

determining a second quantity of HARQ ACKs in the ACK bundle, and

dynamically generating a second acknowledgement timer value thatcorresponds to the second plurality of TBs and the second quantity ofHARQ ACKs in the ACK bundle and that is different from the firstacknowledgement timer value.

61. The method of any of embodiments 54-60, wherein the communicationnetwork comprises a narrow band internet of things network, NBIoT.

62. The method of any of embodiments 54-60, wherein the communicationnetwork comprises an enhanced Machine Type Communication, eMTC, network.

63. A radio access network, RAN, node comprising:

processing circuitry; and

memory coupled with the processing circuitry, wherein the memoryincludes instructions that when executed by the processing circuitrycauses the RAN node to perform operations according to any ofEmbodiments 54-60.

64. A radio access network, RAN, node adapted to perform according toany of Embodiments 54-60.

65. A computer program comprising program code to be executed byprocessing circuitry of a radio access network, RAN, node, wherebyexecution of the program code causes the RAN node to perform operationsaccording to any of embodiments 54-60.

66. A computer program product comprising a non-transitory storagemedium including program code to be executed by processing circuitry ofa radio access network, RAN, node, whereby execution of the program codecauses the RAN node to perform operations according to any ofembodiments 54-60.

67. A method of operating a core network, CN, node configured to operatein a communication network, the method comprising:

sending, to a UE, a scheduling message that includes a scheduleidentifying a plurality of transmission blocks, TBs, that causes the UEto determine a quantity of the plurality of TBs that are identified inthe scheduling message, and that causes the UE to determine a quantityof HARQ ACKs in an ACK bundle identified in the scheduling message andto dynamically generate an acknowledgement timer value that correspondsto the quantity of the plurality of TBs and the quantity of HARQ ACKs inthe ACK bundle.

68. The method of embodiment 67, wherein the acknowledgement timer valueis a function of the quantity of the plurality of transmission blocksand the quantity of HARQ ACKs in the ACK bundle.

69. The method of any of embodiments 67 and 68, wherein the schedulingmessage comprises a downlink control indication, DCI.

70. The method of any of embodiments 67-69, wherein the acknowledgementtimer value comprises a product from multiplying a portion of a timervalue by the quantity of the plurality of TBs in the scheduling messageand quantity of HARQ ACKs in the ACK bundle.

71. The method of any of embodiments 67-70, wherein the acknowledgementtimer value comprises a Hybrid Automatic Repeat Request Round Trip Time,HARQ RTT, timer value that is generated as 7+N*m in which N is aPhysical Uplink Control Channel, PUCCH, repetition factor, and m is thenumber of HARQ ACK bundles identified in the scheduling message, and

wherein m is generated as l/i in which l is the quantity of theplurality of TBs identified in the scheduling message and i is thequantity of HARQ ACKs per ACK bundle.

72. The method of any of embodiments 67-71, wherein the acknowledgementtimer value comprises a Hybrid Automatic Repeat Request Round Trip Time,HARQ RTT, timer value that is generated as 7+N*m+s in which N is aPhysical Uplink Control Channel, PUCCH, repetition factor, m is thenumber of HARQ ACK bundles identified in the scheduling message, and sis a delay factor that provides timer alignment corresponding to machinetype communication physical downlink control channel, MPDCCH,operations, and

wherein m is generated as l/i in which l is the quantity of theplurality of TBs identified in the scheduling message and i is thequantity of HARQ ACKs per ACK bundle.

73. The method of any of embodiments 67-72, wherein the plurality of TBscomprises a first plurality of TB's,

wherein the plurality of TBs comprises a first plurality of TB's,

wherein the quantity of the plurality of TB's comprises a first quantityof TBs,

wherein the quantity of HARQ ACKs in the ACK bundle comprises a firstquantity of HARQ ACKs in the ACK bundle, and

wherein the acknowledgement timer value comprises a firstacknowledgement timer value,

the method further comprising:

receiving a second scheduling message that includes a second scheduleidentifying a second plurality of TBs;

determining a second quantity of the plurality of TBs that areidentified in the second scheduling message;

determining a second quantity of HARQ ACKs in the ACK bundle, and

dynamically generating a second acknowledgement timer value thatcorresponds to the second plurality of TBs and the second quantity ofHARQ ACKs in the ACK bundle and that is different from the firstacknowledgement timer value.

74. The method of any of embodiments 67-73, wherein the communicationnetwork comprises a narrow band internet of things network, NBIoT.

75. The method of any of embodiments 67-74, wherein the communicationnetwork comprises an enhanced Machine Type Communication, eMTC, network.

76. A core network, CN, node comprising:

processing circuitry; and

memory coupled with the processing circuitry, wherein the memoryincludes instructions that when executed by the processing circuitrycauses the CN node to perform operations according to any of Embodiments67-73.

77. A core network, CN, node adapted to perform according to any ofEmbodiments 67-73.

78. A computer program comprising program code to be executed byprocessing circuitry of a core network, CN, node, whereby execution ofthe program code causes the CN node to perform operations according toany of embodiments 67-73.

79. A computer program product comprising a non-transitory storagemedium including program code to be executed by processing circuitry ofa core network, CN, node, whereby execution of the program code causesthe CN node to perform operations according to any of embodiments 67-73.

Explanations are provided below for various abbreviations/acronyms usedin the present disclosure.

Abbreviation Explanation 3GPP 3rd Generation Partnership Project 5G 5thGeneration 5GC 5G Core network AMF Access and Mobility managementFunction AS Access Stratum BRSRP Beam level Reference Signal ReceivedPower BRSRQ Beam level Reference Signal Received Quality BSINR Beamlevel Signal to Noise Ratio CCO Coverage Capacity Optimization CEControl Element CBRA Contention Based Random Access CFRA Contention FreeRandom Access CHO Conditional Handover CN Core Network C-RNTI Cell RadioNetwork Temporary Identifier CSI-RS Channel State Information ReferenceSignal CU Central Unit dB decibel DCI Downlink Control Indication DCDual Connectivity DL Downlink DU Distributed Unit eMTC enhanced MachineType Communication eNB eNodeB eNodeB Evolved NodeB EPC Evolved PacketCore EUTRA/ Evolved Universal Terrestrial Radio Access E-UTRA EUTRAN/Evolved Universal Terrestrial Radio Access Network E-UTRAN FFS ForFurther Study gNB/gNodeB A radio base station in NR. GERAN GSM/EDGERadio Access Network GNSS Global Navigation Satellite System GPRSGeneral Packet Radio Service GTP GPRS Tunneling Protocol HARQ HybridAutomatic Repeat Request HO Handover IE Information Element IoT Internetof Things LTE Long Term Evolution L2 Layer 2 L3 Layer 3 MAC MediumAccess Control MAC CE MAC Control Element MCG Master Cell Group MDTMinimization of drive tests MME Mobility Management Entity MSG MessageMRO Mobility Robustness Optimization NAS Non-access Stratum NB-IoTNarrow Band Internet of Things NG The interface/reference point betweenNG-RAN and 5GC. NGAP Application Protocol/Next Generation ApplicationProtocol NG-RAN Next Generation Radio Access Network NR New Radio OAMOperation and Management PCell Primary Cell (i.e. the primary cell of aMCG) PLMN Public Land Mobile Network PSCell Primary Secondary Cell (i.e.the primary cell of a SCG) QoS Quality of Service RA Random Access RARRandom Access Response RACH Random Access Channel RAN Radio AccessNetwork RAT Radio Access Technology RLC Radio Link Control RLE RadioLink Failure RRC Radio Resource Control RRM Radio Resource Management RSReference Signal RSRP Reference Signal Received Power RSRQ ReferenceSignal Received Quality RTT Round Trip Time S1 The interface/referencepoint between E-UTRAN and EPC. RSSI Received Signal Strength IndicatorSCell Secondary Cell SCG Secondary Cell Group SC-PTM Single Cell Pointto Multipoint SINR Signal to Interference and Noise Ratio SpCell SpecialCell, i.e. either a PCell or a PSCell. SN Sequence Number SRB SignalingRadio Bearer SSB Synchronization Signal Block TA TimingAdjustment/Advance TB Transmission Block TCE Trace Collection Entity TSTechnical Specification UE User Equipment UL UplinkAdditional explanation is provided below.

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

Some of the embodiments contemplated herein will now be described morefully with reference to the accompanying drawings. Other embodiments,however, are contained within the scope of the subject matter disclosedherein, the disclosed subject matter should not be construed as limitedto only the embodiments set forth herein; rather, these embodiments areprovided by way of example to convey the scope of the subject matter tothose skilled in the art.

FIG. 11 illustrates a wireless network in accordance with someembodiments.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 11 .For simplicity, the wireless network of FIG. 11 only depicts network4106, network nodes 4160 and 4160 b, and WDs 4110, 4110 b, and 4110 c(also referred to as mobile terminals). In practice, a wireless networkmay further include any additional elements suitable to supportcommunication between wireless devices or between a wireless device andanother communication device, such as a landline telephone, a serviceprovider, or any other network node or end device. Of the illustratedcomponents, network node 4160 and wireless device (WD) 4110 are depictedwith additional detail. The wireless network may provide communicationand other types of services to one or more wireless devices tofacilitate the wireless devices' access to and/or use of the servicesprovided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork may be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network may implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless localarea network (WLAN) standards, such as the IEEE 802.11 standards; and/orany other appropriate wireless communication standard, such as theWorldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave and/or ZigBee standards.

Network 4106 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node 4160 and WD 4110 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network may comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, access points (APs) (e.g., radio access points), basestations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs(eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based onthe amount of coverage they provide (or, stated differently, theirtransmit power level) and may then also be referred to as femto basestations, pico base stations, micro base stations, or macro basestations. A base station may be a relay node or a relay donor nodecontrolling a relay. A network node may also include one or more (orall) parts of a distributed radio base station such as centralizeddigital units and/or remote radio units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such remote radio units may or may not beintegrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station may also be referred to as nodes in adistributed antenna system (DAS). Yet further examples of network nodesinclude multi-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As anotherexample, a network node may be a virtual network node as described inmore detail below. More generally, however, network nodes may representany suitable device (or group of devices) capable, configured, arranged,and/or operable to enable and/or provide a wireless device with accessto the wireless network or to provide some service to a wireless devicethat has accessed the wireless network.

In FIG. 11 , network node 4160 includes processing circuitry 4170,device readable medium 4180, interface 4190, auxiliary equipment 4184,power source 4186, power circuitry 4187, and antenna 4162. Althoughnetwork node 4160 illustrated in the example wireless network of FIG. 11may represent a device that includes the illustrated combination ofhardware components, other embodiments may comprise network nodes withdifferent combinations of components. It is to be understood that anetwork node comprises any suitable combination of hardware and/orsoftware needed to perform the tasks, features, functions and methodsdisclosed herein. Moreover, while the components of network node 4160are depicted as single boxes located within a larger box, or nestedwithin multiple boxes, in practice, a network node may comprise multipledifferent physical components that make up a single illustratedcomponent (e.g., device readable medium 4180 may comprise multipleseparate hard drives as well as multiple RAM modules).

Similarly, network node 4160 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node 4160comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node. In someembodiments, network node 4160 may be configured to support multipleradio access technologies (RATs). In such embodiments, some componentsmay be duplicated (e.g., separate device readable medium 4180 for thedifferent RATs) and some components may be reused (e.g., the sameantenna 4162 may be shared by the RATs). Network node 4160 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node 4160, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into thesame or different chip or set of chips and other components withinnetwork node 4160.

Processing circuitry 4170 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry 4170 may include processinginformation obtained by processing circuitry 4170 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedin the network node, and/or performing one or more operations based onthe obtained information or converted information, and as a result ofsaid processing making a determination.

Processing circuitry 4170 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode 4160 components, such as device readable medium 4180, network node4160 functionality. For example, processing circuitry 4170 may executeinstructions stored in device readable medium 4180 or in memory withinprocessing circuitry 4170. Such functionality may include providing anyof the various wireless features, functions, or benefits discussedherein. In some embodiments, processing circuitry 4170 may include asystem on a chip (SOC).

In some embodiments, processing circuitry 4170 may include one or moreof radio frequency (RF) transceiver circuitry 4172 and basebandprocessing circuitry 4174. In some embodiments, radio frequency (RF)transceiver circuitry 4172 and baseband processing circuitry 4174 may beon separate chips (or sets of chips), boards, or units, such as radiounits and digital units. In alternative embodiments, part or all of RFtransceiver circuitry 4172 and baseband processing circuitry 4174 may beon the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry 4170executing instructions stored on device readable medium 4180 or memorywithin processing circuitry 4170. In alternative embodiments, some orall of the functionality may be provided by processing circuitry 4170without executing instructions stored on a separate or discrete devicereadable medium, such as in a hard-wired manner. In any of thoseembodiments, whether executing instructions stored on a device readablestorage medium or not, processing circuitry 4170 can be configured toperform the described functionality. The benefits provided by suchfunctionality are not limited to processing circuitry 4170 alone or toother components of network node 4160, but are enjoyed by network node4160 as a whole, and/or by end users and the wireless network generally.

Device readable medium 4180 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry 4170. Device readable medium 4180 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry 4170 and, utilized by network node 4160. Devicereadable medium 4180 may be used to store any calculations made byprocessing circuitry 4170 and/or any data received via interface 4190.In some embodiments, processing circuitry 4170 and device readablemedium 4180 may be considered to be integrated.

Interface 4190 is used in the wired or wireless communication ofsignalling and/or data between network node 4160, network 4106, and/orWDs 4110. As illustrated, interface 4190 comprises port(s)/terminal(s)4194 to send and receive data, for example to and from network 4106 overa wired connection. Interface 4190 also includes radio front endcircuitry 4192 that may be coupled to, or in certain embodiments a partof, antenna 4162. Radio front end circuitry 4192 comprises filters 4198and amplifiers 4196. Radio front end circuitry 4192 may be connected toantenna 4162 and processing circuitry 4170. Radio front end circuitrymay be configured to condition signals communicated between antenna 4162and processing circuitry 4170. Radio front end circuitry 4192 mayreceive digital data that is to be sent out to other network nodes orWDs via a wireless connection. Radio front end circuitry 4192 mayconvert the digital data into a radio signal having the appropriatechannel and bandwidth parameters using a combination of filters 4198and/or amplifiers 4196. The radio signal may then be transmitted viaantenna 4162. Similarly, when receiving data, antenna 4162 may collectradio signals which are then converted into digital data by radio frontend circuitry 4192. The digital data may be passed to processingcircuitry 4170. In other embodiments, the interface may comprisedifferent components and/or different combinations of components.

In certain alternative embodiments, network node 4160 may not includeseparate radio front end circuitry 4192, instead, processing circuitry4170 may comprise radio front end circuitry and may be connected toantenna 4162 without separate radio front end circuitry 4192. Similarly,in some embodiments, all or some of RF transceiver circuitry 4172 may beconsidered a part of interface 4190. In still other embodiments,interface 4190 may include one or more ports or terminals 4194, radiofront end circuitry 4192, and RF transceiver circuitry 4172, as part ofa radio unit (not shown), and interface 4190 may communicate withbaseband processing circuitry 4174, which is part of a digital unit (notshown).

Antenna 4162 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna 4162 may becoupled to radio front end circuitry 4192 and may be any type of antennacapable of transmitting and receiving data and/or signals wirelessly. Insome embodiments, antenna 4162 may comprise one or moreomni-directional, sector or panel antennas operable to transmit/receiveradio signals between, for example, 2 GHz and 66 GHz. Anomni-directional antenna may be used to transmit/receive radio signalsin any direction, a sector antenna may be used to transmit/receive radiosignals from devices within a particular area, and a panel antenna maybe a line of sight antenna used to transmit/receive radio signals in arelatively straight line. In some instances, the use of more than oneantenna may be referred to as MIMO. In certain embodiments, antenna 4162may be separate from network node 4160 and may be connectable to networknode 4160 through an interface or port.

Antenna 4162, interface 4190, and/or processing circuitry 4170 may beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna 4162, interface 4190, and/or processing circuitry 4170 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry 4187 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network node4160 with power for performing the functionality described herein. Powercircuitry 4187 may receive power from power source 4186. Power source4186 and/or power circuitry 4187 may be configured to provide power tothe various components of network node 4160 in a form suitable for therespective components (e.g., at a voltage and current level needed foreach respective component). Power source 4186 may either be included in,or external to, power circuitry 4187 and/or network node 4160. Forexample, network node 4160 may be connectable to an external powersource (e.g., an electricity outlet) via an input circuitry or interfacesuch as an electrical cable, whereby the external power source suppliespower to power circuitry 4187. As a further example, power source 4186may comprise a source of power in the form of a battery or battery packwhich is connected to, or integrated in, power circuitry 4187. Thebattery may provide backup power should the external power source fail.Other types of power sources, such as photovoltaic devices, may also beused.

Alternative embodiments of network node 4160 may include additionalcomponents beyond those shown in FIG. 11 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node 4160 may include user interface equipment to allow input ofinformation into network node 4160 and to allow output of informationfrom network node 4160. This may allow a user to perform diagnostic,maintenance, repair, and other administrative functions for network node4160.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD may be used interchangeably herein with user equipment (UE).Communicating wirelessly may involve transmitting and/or receivingwireless signals using electromagnetic waves, radio waves, infraredwaves, and/or other types of signals suitable for conveying informationthrough air. In some embodiments, a WD may be configured to transmitand/or receive information without direct human interaction. Forinstance, a WD may be designed to transmit information to a network on apredetermined schedule, when triggered by an internal or external event,or in response to requests from the network. Examples of a WD include,but are not limited to, a smart phone, a mobile phone, a cell phone, avoice over IP (VoIP) phone, a wireless local loop phone, a desktopcomputer, a personal digital assistant (PDA), a wireless cameras, agaming console or device, a music storage device, a playback appliance,a wearable terminal device, a wireless endpoint, a mobile station, atablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mountedequipment (LME), a smart device, a wireless customer-premise equipment(CPE). a vehicle-mounted wireless terminal device, etc. A WD may supportdevice-to-device (D2D) communication, for example by implementing a 3GPPstandard for sidelink communication, vehicle-to-vehicle (V2V),vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may inthis case be referred to as a D2D communication device. As yet anotherspecific example, in an Internet of Things (IoT) scenario, a WD mayrepresent a machine or other device that performs monitoring and/ormeasurements, and transmits the results of such monitoring and/ormeasurements to another WD and/or a network node. The WD may in thiscase be a machine-to-machine (M2M) device, which may in a 3GPP contextbe referred to as an MTC device. As one particular example, the WD maybe a UE implementing the 3GPP narrow band internet of things (NB-IoT)standard. Particular examples of such machines or devices are sensors,metering devices such as power meters, industrial machinery, or home orpersonal appliances (e.g. refrigerators, televisions, etc.) personalwearables (e.g., watches, fitness trackers, etc.). In other scenarios, aWD may represent a vehicle or other equipment that is capable ofmonitoring and/or reporting on its operational status or other functionsassociated with its operation. A WD as described above may represent theendpoint of a wireless connection, in which case the device may bereferred to as a wireless terminal. Furthermore, a WD as described abovemay be mobile, in which case it may also be referred to as a mobiledevice or a mobile terminal.

As illustrated, wireless device 4110 includes antenna 4111, interface4114, processing circuitry 4120, device readable medium 4130, userinterface equipment 4132, auxiliary equipment 4134, power source 4136and power circuitry 4137. WD 4110 may include multiple sets of one ormore of the illustrated components for different wireless technologiessupported by WD 4110, such as, for example, GSM, WCDMA, LTE, NR, WiFi,WiMAX, or Bluetooth wireless technologies, just to mention a few. Thesewireless technologies may be integrated into the same or different chipsor set of chips as other components within WD 4110.

Antenna 4111 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface 4114. In certain alternative embodiments, antenna 4111 may beseparate from WD 4110 and be connectable to WD 4110 through an interfaceor port. Antenna 4111, interface 4114, and/or processing circuitry 4120may be configured to perform any receiving or transmitting operationsdescribed herein as being performed by a WD. Any information, dataand/or signals may be received from a network node and/or another WD. Insome embodiments, radio front end circuitry and/or antenna 4111 may beconsidered an interface.

As illustrated, interface 4114 comprises radio front end circuitry 4112and antenna 4111. Radio front end circuitry 4112 comprise one or morefilters 4118 and amplifiers 4116. Radio front end circuitry 4112 isconnected to antenna 4111 and processing circuitry 4120, and isconfigured to condition signals communicated between antenna 4111 andprocessing circuitry 4120. Radio front end circuitry 4112 may be coupledto or a part of antenna 4111. In some embodiments, WD 4110 may notinclude separate radio front end circuitry 4112; rather, processingcircuitry 4120 may comprise radio front end circuitry and may beconnected to antenna 4111. Similarly, in some embodiments, some or allof RF transceiver circuitry 4122 may be considered a part of interface4114. Radio front end circuitry 4112 may receive digital data that is tobe sent out to other network nodes or WDs via a wireless connection.Radio front end circuitry 4112 may convert the digital data into a radiosignal having the appropriate channel and bandwidth parameters using acombination of filters 4118 and/or amplifiers 4116. The radio signal maythen be transmitted via antenna 4111. Similarly, when receiving data,antenna 4111 may collect radio signals which are then converted intodigital data by radio front end circuitry 4112. The digital data may bepassed to processing circuitry 4120. In other embodiments, the interfacemay comprise different components and/or different combinations ofcomponents.

Processing circuitry 4120 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD 4110components, such as device readable medium 4130, WD 4110 functionality.Such functionality may include providing any of the various wirelessfeatures or benefits discussed herein. For example, processing circuitry4120 may execute instructions stored in device readable medium 4130 orin memory within processing circuitry 4120 to provide the functionalitydisclosed herein.

As illustrated, processing circuitry 4120 includes one or more of RFtransceiver circuitry 4122, baseband processing circuitry 4124, andapplication processing circuitry 4126. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitry4120 of WD 4110 may comprise a SOC. In some embodiments, RF transceivercircuitry 4122, baseband processing circuitry 4124, and applicationprocessing circuitry 4126 may be on separate chips or sets of chips. Inalternative embodiments, part or all of baseband processing circuitry4124 and application processing circuitry 4126 may be combined into onechip or set of chips, and RF transceiver circuitry 4122 may be on aseparate chip or set of chips. In still alternative embodiments, part orall of RF transceiver circuitry 4122 and baseband processing circuitry4124 may be on the same chip or set of chips, and application processingcircuitry 4126 may be on a separate chip or set of chips. In yet otheralternative embodiments, part or all of RF transceiver circuitry 4122,baseband processing circuitry 4124, and application processing circuitry4126 may be combined in the same chip or set of chips. In someembodiments, RF transceiver circuitry 4122 may be a part of interface4114. RF transceiver circuitry 4122 may condition RF signals forprocessing circuitry 4120.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry 4120 executing instructions stored on device readable medium4130, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry 4120 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry 4120 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry 4120 alone or to other components ofWD 4110, but are enjoyed by WD 4110 as a whole, and/or by end users andthe wireless network generally.

Processing circuitry 4120 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry 4120, may include processinginformation obtained by processing circuitry 4120 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD 4110, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium 4130 may be operable to store a computer program,software, an application including one or more of logic, rules, code,tables, etc. and/or other instructions capable of being executed byprocessing circuitry 4120. Device readable medium 4130 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry 4120. In someembodiments, processing circuitry 4120 and device readable medium 4130may be considered to be integrated.

User interface equipment 4132 may provide components that allow for ahuman user to interact with WD 4110. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipment4132 may be operable to produce output to the user and to allow the userto provide input to WD 4110. The type of interaction may vary dependingon the type of user interface equipment 4132 installed in WD 4110. Forexample, if WD 4110 is a smart phone, the interaction may be via a touchscreen; if WD 4110 is a smart meter, the interaction may be through ascreen that provides usage (e.g., the number of gallons used) or aspeaker that provides an audible alert (e.g., if smoke is detected).User interface equipment 4132 may include input interfaces, devices andcircuits, and output interfaces, devices and circuits. User interfaceequipment 4132 is configured to allow input of information into WD 4110,and is connected to processing circuitry 4120 to allow processingcircuitry 4120 to process the input information. User interfaceequipment 4132 may include, for example, a microphone, a proximity orother sensor, keys/buttons, a touch display, one or more cameras, a USBport, or other input circuitry. User interface equipment 4132 is alsoconfigured to allow output of information from WD 4110, and to allowprocessing circuitry 4120 to output information from WD 4110. Userinterface equipment 4132 may include, for example, a speaker, a display,vibrating circuitry, a USB port, a headphone interface, or other outputcircuitry. Using one or more input and output interfaces, devices, andcircuits, of user interface equipment 4132, WD 4110 may communicate withend users and/or the wireless network, and allow them to benefit fromthe functionality described herein.

Auxiliary equipment 4134 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment 4134 may vary depending on the embodiment and/or scenario.

Power source 4136 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD 4110 may further comprise power circuitry4137 for delivering power from power source 4136 to the various parts ofWD 4110 which need power from power source 4136 to carry out anyfunctionality described or indicated herein. Power circuitry 4137 may incertain embodiments comprise power management circuitry. Power circuitry4137 may additionally or alternatively be operable to receive power froman external power source; in which case WD 4110 may be connectable tothe external power source (such as an electricity outlet) via inputcircuitry or an interface such as an electrical power cable. Powercircuitry 4137 may also in certain embodiments be operable to deliverpower from an external power source to power source 4136. This may be,for example, for the charging of power source 4136. Power circuitry 4137may perform any formatting, converting, or other modification to thepower from power source 4136 to make the power suitable for therespective components of WD 4110 to which power is supplied.

FIG. 12 illustrates a user Equipment in accordance with someembodiments.

FIG. 12 illustrates one embodiment of a UE in accordance with variousaspects described herein. As used herein, a user equipment or UE may notnecessarily have a user in the sense of a human user who owns and/oroperates the relevant device. Instead, a UE may represent a device thatis intended for sale to, or operation by, a human user but which maynot, or which may not initially, be associated with a specific humanuser (e.g., a smart sprinkler controller). Alternatively, a UE mayrepresent a device that is not intended for sale to, or operation by, anend user but which may be associated with or operated for the benefit ofa user (e.g., a smart power meter). UE 42200 may be any UE identified bythe 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, amachine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.UE 4200, as illustrated in FIG. 12 , is one example of a WD configuredfor communication in accordance with one or more communication standardspromulgated by the 3rd Generation Partnership Project (3GPP), such as3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, theterm WD and UE may be used interchangeable. Accordingly, although FIG.12 is a UE, the components discussed herein are equally applicable to aWD, and vice-versa.

In FIG. 12 , UE 4200 includes processing circuitry 4201 that isoperatively coupled to input/output interface 4205, radio frequency (RF)interface 4209, network connection interface 4211, memory 4215 includingrandom access memory (RAM) 4217, read-only memory (ROM) 4219, andstorage medium 4221 or the like, communication subsystem 4231, powersource 4213, and/or any other component, or any combination thereof.Storage medium 4221 includes operating system 4223, application program4225, and data 4227. In other embodiments, storage medium 4221 mayinclude other similar types of information. Certain UEs may utilize allof the components shown in FIG. 12 , or only a subset of the components.The level of integration between the components may vary from one UE toanother UE. Further, certain UEs may contain multiple instances of acomponent, such as multiple processors, memories, transceivers,transmitters, receivers, etc.

In FIG. 12 , processing circuitry 4201 may be configured to processcomputer instructions and data. Processing circuitry 4201 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry 4201 may include twocentral processing units (CPUs). Data may be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface 4205 may beconfigured to provide a communication interface to an input device,output device, or input and output device. UE 4200 may be configured touse an output device via input/output interface 4205. An output devicemay use the same type of interface port as an input device. For example,a USB port may be used to provide input to and output from UE 4200. Theoutput device may be a speaker, a sound card, a video card, a display, amonitor, a printer, an actuator, an emitter, a smartcard, another outputdevice, or any combination thereof. UE 4200 may be configured to use aninput device via input/output interface 4205 to allow a user to captureinformation into UE 4200. The input device may include a touch-sensitiveor presence-sensitive display, a camera (e.g., a digital camera, adigital video camera, a web camera, etc.), a microphone, a sensor, amouse, a trackball, a directional pad, a trackpad, a scroll wheel, asmartcard, and the like. The presence-sensitive display may include acapacitive or resistive touch sensor to sense input from a user. Asensor may be, for instance, an accelerometer, a gyroscope, a tiltsensor, a force sensor, a magnetometer, an optical sensor, a proximitysensor, another like sensor, or any combination thereof. For example,the input device may be an accelerometer, a magnetometer, a digitalcamera, a microphone, and an optical sensor.

In FIG. 12 , RF interface 4209 may be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. Network connection interface 4211 may beconfigured to provide a communication interface to network 4243 a.Network 4243 a may encompass wired and/or wireless networks such as alocal-area network (LAN), a wide-area network (WAN), a computer network,a wireless network, a telecommunications network, another like networkor any combination thereof. For example, network 4243 a may comprise aWi-Fi network. Network connection interface 4211 may be configured toinclude a receiver and a transmitter interface used to communicate withone or more other devices over a communication network according to oneor more communication protocols, such as Ethernet, TCP/IP, SONET, ATM,or the like. Network connection interface 4211 may implement receiverand transmitter functionality appropriate to the communication networklinks (e.g., optical, electrical, and the like). The transmitter andreceiver functions may share circuit components, software or firmware,or alternatively may be implemented separately.

RAM 4217 may be configured to interface via bus 4202 to processingcircuitry 4201 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM 4219 maybe configured to provide computer instructions or data to processingcircuitry 4201. For example, ROM 4219 may be configured to storeinvariant low-level system code or data for basic system functions suchas basic input and output (I/O), startup, or reception of keystrokesfrom a keyboard that are stored in a non-volatile memory. Storage medium4221 may be configured to include memory such as RAM, ROM, programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium 4221 may be configured toinclude operating system 4223, application program 4225 such as a webbrowser application, a widget or gadget engine or another application,and data file 4227. Storage medium 4221 may store, for use by UE 4200,any of a variety of various operating systems or combinations ofoperating systems.

Storage medium 4221 may be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium 4221 may allow UE 4200 to access computer-executableinstructions, application programs or the like, stored on transitory ornon-transitory memory media, to off-load data, or to upload data. Anarticle of manufacture, such as one utilizing a communication system maybe tangibly embodied in storage medium 4221, which may comprise a devicereadable medium.

In FIG. 12 , processing circuitry 4201 may be configured to communicatewith network 4243 b using communication subsystem 4231. Network 4243 aand network 4243 b may be the same network or networks or differentnetwork or networks. Communication subsystem 4231 may be configured toinclude one or more transceivers used to communicate with network 4243b. For example, communication subsystem 4231 may be configured toinclude one or more transceivers used to communicate with one or moreremote transceivers of another device capable of wireless communicationsuch as another WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.11,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver mayinclude transmitter 4233 and/or receiver 4235 to implement transmitteror receiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter 4233and receiver 4235 of each transceiver may share circuit components,software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem 4231 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem 4231 may include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network 4243 b may encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, network4243 b may be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source 4213 may be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE 4200.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE 4200 or partitioned acrossmultiple components of UE 4200. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystem4231 may be configured to include any of the components describedherein. Further, processing circuitry 4201 may be configured tocommunicate with any of such components over bus 4202. In anotherexample, any of such components may be represented by programinstructions stored in memory that when executed by processing circuitry4201 perform the corresponding functions described herein. In anotherexample, the functionality of any of such components may be partitionedbetween processing circuitry 4201 and communication subsystem 4231. Inanother example, the non-computationally intensive functions of any ofsuch components may be implemented in software or firmware and thecomputationally intensive functions may be implemented in hardware.

FIG. 13 illustrates a virtualization environment in accordance with someembodiments.

FIG. 13 is a schematic block diagram illustrating a virtualizationenvironment 4300 in which functions implemented by some embodiments maybe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments 4300 hosted byone or more of hardware nodes 4330. Further, in embodiments in which thevirtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications 4320 (whichmay alternatively be called software instances, virtual appliances,network functions, virtual nodes, virtual network functions, etc.)operative to implement some of the features, functions, and/or benefitsof some of the embodiments disclosed herein. Applications 4320 are runin virtualization environment 4300 which provides hardware 4330comprising processing circuitry 4360 and memory 4390. Memory 4390contains instructions 4395 executable by processing circuitry 4360whereby application 4320 is operative to provide one or more of thefeatures, benefits, and/or functions disclosed herein.

Virtualization environment 4300, comprises general-purpose orspecial-purpose network hardware devices 4330 comprising a set of one ormore processors or processing circuitry 4360, which may be commercialoff-the-shelf (COTS) processors, dedicated Application SpecificIntegrated Circuits (ASICs), or any other type of processing circuitryincluding digital or analog hardware components or special purposeprocessors. Each hardware device may comprise memory 4390-1 which may benon-persistent memory for temporarily storing instructions 4395 orsoftware executed by processing circuitry 4360. Each hardware device maycomprise one or more network interface controllers (NICs) 4370, alsoknown as network interface cards, which include physical networkinterface 4380. Each hardware device may also include non-transitory,persistent, machine-readable storage media 4390-2 having stored thereinsoftware 4395 and/or instructions executable by processing circuitry4360. Software 4395 may include any type of software including softwarefor instantiating one or more virtualization layers 4350 (also referredto as hypervisors), software to execute virtual machines 4340 as well assoftware allowing it to execute functions, features and/or benefitsdescribed in relation with some embodiments described herein.

Virtual machines 4340 comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer 4350 or hypervisor. Differentembodiments of the instance of virtual appliance 4320 may be implementedon one or more of virtual machines 4340, and the implementations may bemade in different ways.

During operation, processing circuitry 4360 executes software 4395 toinstantiate the hypervisor or virtualization layer 4350, which maysometimes be referred to as a virtual machine monitor (VMM).Virtualization layer 4350 may present a virtual operating platform thatappears like networking hardware to virtual machine 4340.

As shown in FIG. 13 , hardware 4330 may be a standalone network nodewith generic or specific components. Hardware 4330 may comprise antenna43225 and may implement some functions via virtualization.Alternatively, hardware 4330 may be part of a larger cluster of hardware(e.g. such as in a data center or customer premise equipment (CPE))where many hardware nodes work together and are managed via managementand orchestration (MANO) 43100, which, among others, oversees lifecyclemanagement of applications 4320.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine 4340 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines 4340, and that part of hardware 4330 that executes that virtualmachine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines 4340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines 4340 on top of hardware networking infrastructure4330 and corresponds to application 4320 in FIG. 13 .

In some embodiments, one or more radio units 43200 that each include oneor more transmitters 43220 and one or more receivers 43210 may becoupled to one or more antennas 43225. Radio units 43200 may communicatedirectly with hardware nodes 4330 via one or more appropriate networkinterfaces and may be used in combination with the virtual components toprovide a virtual node with radio capabilities, such as a radio accessnode or a base station.

In some embodiments, some signalling can be effected with the use ofcontrol system 43230 which may alternatively be used for communicationbetween the hardware nodes 4330 and radio units 43200.

FIG. 14 illustrates a telecommunication network connected via anintermediate network to a host computer in accordance with someembodiments.

With reference to FIG. 14 , in accordance with an embodiment, acommunication system includes telecommunication network 4410, such as a3GPP-type cellular network, which comprises access network 4411, such asa radio access network, and core network 4414. Access network 4411comprises a plurality of base stations 4412 a, 4412 b, 4412 c, such asNBs, eNBs, gNBs or other types of wireless access points, each defininga corresponding coverage area 4413 a, 4413 b, 4413 c. Each base station4412 a, 4412 b, 4412 c is connectable to core network 4414 over a wiredor wireless connection 4415. A first UE 4491 located in coverage area4413 c is configured to wirelessly connect to, or be paged by, thecorresponding base station 4412 c. A second UE 4492 in coverage area4413 a is wirelessly connectable to the corresponding base station 4412a. While a plurality of UEs 4491, 4492 are illustrated in this example,the disclosed embodiments are equally applicable to a situation where asole UE is in the coverage area or where a sole UE is connecting to thecorresponding base station 4412.

Telecommunication network 4410 is itself connected to host computer4430, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. Host computer 4430 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider.Connections 4421 and 4422 between telecommunication network 4410 andhost computer 4430 may extend directly from core network 4414 to hostcomputer 4430 or may go via an optional intermediate network 4420.Intermediate network 4420 may be one of, or a combination of more thanone of, a public, private or hosted network; intermediate network 4420,if any, may be a backbone network or the Internet; in particular,intermediate network 4420 may comprise two or more sub-networks (notshown).

The communication system of FIG. 14 as a whole enables connectivitybetween the connected UEs 4491, 4492 and host computer 4430. Theconnectivity may be described as an over-the-top (OTT) connection 4450.Host computer 4430 and the connected UEs 4491, 4492 are configured tocommunicate data and/or signaling via OTT connection 4450, using accessnetwork 4411, core network 4414, any intermediate network 4420 andpossible further infrastructure (not shown) as intermediaries. OTTconnection 4450 may be transparent in the sense that the participatingcommunication devices through which OTT connection 4450 passes areunaware of routing of uplink and downlink communications. For example,base station 4412 may not or need not be informed about the past routingof an incoming downlink communication with data originating from hostcomputer 4430 to be forwarded (e.g., handed over) to a connected UE4491. Similarly, base station 4412 need not be aware of the futurerouting of an outgoing uplink communication originating from the UE 4491towards the host computer 4430.

FIG. 15 illustrates a host computer communicating via a base stationwith a user equipment over a partially wireless connection in accordancewith some embodiments.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 15 . In communicationsystem 4500, host computer 4510 comprises hardware 4515 includingcommunication interface 4516 configured to set up and maintain a wiredor wireless connection with an interface of a different communicationdevice of communication system 4500. Host computer 4510 furthercomprises processing circuitry 4518, which may have storage and/orprocessing capabilities. In particular, processing circuitry 4518 maycomprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. Host computer 4510further comprises software 4511, which is stored in or accessible byhost computer 4510 and executable by processing circuitry 4518. Software4511 includes host application 4512. Host application 4512 may beoperable to provide a service to a remote user, such as UE 4530connecting via OTT connection 4550 terminating at UE 4530 and hostcomputer 4510. In providing the service to the remote user, hostapplication 4512 may provide user data which is transmitted using OTTconnection 4550.

Communication system 4500 further includes base station 4520 provided ina telecommunication system and comprising hardware 4525 enabling it tocommunicate with host computer 4510 and with UE 4530. Hardware 4525 mayinclude communication interface 4526 for setting up and maintaining awired or wireless connection with an interface of a differentcommunication device of communication system 4500, as well as radiointerface 4527 for setting up and maintaining at least wirelessconnection 4570 with UE 4530 located in a coverage area (not shown inFIG. 15 ) served by base station 4520. Communication interface 4526 maybe configured to facilitate connection 4560 to host computer 4510.Connection 4560 may be direct or it may pass through a core network (notshown in FIG. 15 ) of the telecommunication system and/or through one ormore intermediate networks outside the telecommunication system. In theembodiment shown, hardware 4525 of base station 4520 further includesprocessing circuitry 4528, which may comprise one or more programmableprocessors, application-specific integrated circuits, field programmablegate arrays or combinations of these (not shown) adapted to executeinstructions. Base station 4520 further has software 4521 storedinternally or accessible via an external connection.

Communication system 4500 further includes UE 4530 already referred to.Its hardware 4535 may include radio interface 4537 configured to set upand maintain wireless connection 4570 with a base station serving acoverage area in which UE 4530 is currently located. Hardware 4535 of UE4530 further includes processing circuitry 4538, which may comprise oneor more programmable processors, application-specific integratedcircuits, field programmable gate arrays or combinations of these (notshown) adapted to execute instructions. UE 4530 further comprisessoftware 4531, which is stored in or accessible by UE 4530 andexecutable by processing circuitry 4538. Software 4531 includes clientapplication 4532. Client application 4532 may be operable to provide aservice to a human or non-human user via UE 4530, with the support ofhost computer 4510. In host computer 4510, an executing host application4512 may communicate with the executing client application 4532 via OTTconnection 4550 terminating at UE 4530 and host computer 4510. Inproviding the service to the user, client application 4532 may receiverequest data from host application 4512 and provide user data inresponse to the request data. OTT connection 4550 may transfer both therequest data and the user data. Client application 4532 may interactwith the user to generate the user data that it provides.

It is noted that host computer 4510, base station 4520 and UE 4530illustrated in FIG. 15 may be similar or identical to host computer4430, one of base stations 4412 a, 4412 b, 4412 c and one of UEs 4491,4492 of FIG. 14 , respectively. This is to say, the inner workings ofthese entities may be as shown in FIG. 15 and independently, thesurrounding network topology may be that of FIG. 14 .

In FIG. 15 , OTT connection 4550 has been drawn abstractly to illustratethe communication between host computer 4510 and UE 4530 via basestation 4520, without explicit reference to any intermediary devices andthe precise routing of messages via these devices. Networkinfrastructure may determine the routing, which it may be configured tohide from UE 4530 or from the service provider operating host computer4510, or both. While OTT connection 4550 is active, the networkinfrastructure may further take decisions by which it dynamicallychanges the routing (e.g., on the basis of load balancing considerationor reconfiguration of the network).

Wireless connection 4570 between UE 4530 and base station 4520 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments may improve theperformance of OTT services provided to UE 4530 using OTT connection4550, in which wireless connection 4570 forms the last segment. Moreprecisely, the teachings of these embodiments may improve the randomaccess speed and/or reduce random access failure rates and therebyprovide benefits such as faster and/or more reliable random access.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring OTT connection 4550 between hostcomputer 4510 and UE 4530, in response to variations in the measurementresults. The measurement procedure and/or the network functionality forreconfiguring OTT connection 4550 may be implemented in software 4511and hardware 4515 of host computer 4510 or in software 4531 and hardware4535 of UE 4530, or both. In embodiments, sensors (not shown) may bedeployed in or in association with communication devices through whichOTT connection 4550 passes; the sensors may participate in themeasurement procedure by supplying values of the monitored quantitiesexemplified above, or supplying values of other physical quantities fromwhich software 4511, 4531 may compute or estimate the monitoredquantities. The reconfiguring of OTT connection 4550 may include messageformat, retransmission settings, preferred routing etc.; thereconfiguring need not affect base station 4520, and it may be unknownor imperceptible to base station 4520. Such procedures andfunctionalities may be known and practiced in the art. In certainembodiments, measurements may involve proprietary UE signalingfacilitating host computer 4510's measurements of throughput,propagation times, latency and the like. The measurements may beimplemented in that software 4511 and 4531 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection 4550 while it monitors propagation times, errors etc.

FIG. 16 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments

FIG. 16 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 14 and 15 . Forsimplicity of the present disclosure, only drawing references to FIG. 16will be included in this section. In step 4610, the host computerprovides user data. In substep 4611 (which may be optional) of step4610, the host computer provides the user data by executing a hostapplication. In step 4620, the host computer initiates a transmissioncarrying the user data to the UE. In step 4630 (which may be optional),the base station transmits to the UE the user data which was carried inthe transmission that the host computer initiated, in accordance withthe teachings of the embodiments described throughout this disclosure.In step 4640 (which may also be optional), the UE executes a clientapplication associated with the host application executed by the hostcomputer.

FIG. 17 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments.

FIG. 17 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 14 and 15 . Forsimplicity of the present disclosure, only drawing references to FIG. 17will be included in this section. In step 4710 of the method, the hostcomputer provides user data. In an optional substep (not shown) the hostcomputer provides the user data by executing a host application. In step4720, the host computer initiates a transmission carrying the user datato the UE. The transmission may pass via the base station, in accordancewith the teachings of the embodiments described throughout thisdisclosure. In step 4730 (which may be optional), the UE receives theuser data carried in the transmission.

FIG. 18 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments

FIG. 18 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 14 and 15 . Forsimplicity of the present disclosure, only drawing references to FIG. 18will be included in this section. In step 4810 (which may be optional),the UE receives input data provided by the host computer. Additionallyor alternatively, in step 4820, the UE provides user data. In substep4821 (which may be optional) of step 4820, the UE provides the user databy executing a client application. In substep 4811 (which may beoptional) of step 4810, the UE executes a client application whichprovides the user data in reaction to the received input data providedby the host computer. In providing the user data, the executed clientapplication may further consider user input received from the user.Regardless of the specific manner in which the user data was provided,the UE initiates, in substep 4830 (which may be optional), transmissionof the user data to the host computer. In step 4840 of the method, thehost computer receives the user data transmitted from the UE, inaccordance with the teachings of the embodiments described throughoutthis disclosure.

FIG. 19 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments

FIG. 19 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 14 and 15 . Forsimplicity of the present disclosure, only drawing references to FIG. 19will be included in this section. In step 4910 (which may be optional),in accordance with the teachings of the embodiments described throughoutthis disclosure, the base station receives user data from the UE. Instep 4920 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In step4930 (which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefitsdisclosed herein may be performed through one or more functional unitsor modules of one or more virtual apparatuses. Each virtual apparatusmay comprise a number of these functional units. These functional unitsmay be implemented via processing circuitry, which may include one ormore microprocessor or microcontrollers, as well as other digitalhardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory (RAM), cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein. In some implementations, theprocessing circuitry may be used to cause the respective functional unitto perform corresponding functions according one or more embodiments ofthe present disclosure.

The term unit may have conventional meaning in the field of electronics,electrical devices and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

Further definitions and embodiments are discussed below.

In the above-description of various embodiments of present inventiveconcepts, it is to be understood that the terminology used herein is forthe purpose of describing particular embodiments only and is notintended to be limiting of present inventive concepts. Unless otherwisedefined, all terms (including technical and scientific terms) usedherein have the same meaning as commonly understood by one of ordinaryskill in the art to which present inventive concepts belong. It will befurther understood that terms, such as those defined in commonly useddictionaries, should be interpreted as having a meaning that isconsistent with their meaning in the context of this specification andthe relevant art and will not be interpreted in an idealized or overlyformal sense unless expressly so defined herein.

When an element is referred to as being “connected”, “coupled”,“responsive”, or variants thereof to another element, it can be directlyconnected, coupled, or responsive to the other element or interveningelements may be present. In contrast, when an element is referred to asbeing “directly connected”, “directly coupled”, “directly responsive”,or variants thereof to another element, there are no interveningelements present. Like numbers refer to like elements throughout.Furthermore, “coupled”, “connected”, “responsive”, or variants thereofas used herein may include wirelessly coupled, connected, or responsive.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. Well-known functions or constructions may not be described indetail for brevity and/or clarity. The term “and/or” (abbreviated “/”)includes any and all combinations of one or more of the associatedlisted items.

It will be understood that although the terms first, second, third, etc.may be used herein to describe various elements/operations, theseelements/operations should not be limited by these terms. These termsare only used to distinguish one element/operation from anotherelement/operation. Thus, a first element/operation in some embodimentscould be termed a second element/operation in other embodiments withoutdeparting from the teachings of present inventive concepts. The samereference numerals or the same reference designators denote the same orsimilar elements throughout the specification.

As used herein, the terms “comprise”, “comprising”, “comprises”,“include”, “including”, “includes”, “have”, “has”, “having”, or variantsthereof are open-ended, and include one or more stated features,integers, elements, steps, components or functions but does not precludethe presence or addition of one or more other features, integers,elements, steps, components, functions or groups thereof. Furthermore,as used herein, the common abbreviation “e.g.”, which derives from theLatin phrase “exempli gratia,” may be used to introduce or specify ageneral example or examples of a previously mentioned item, and is notintended to be limiting of such item. The common abbreviation “i.e.”,which derives from the Latin phrase “id est,” may be used to specify aparticular item from a more general recitation.

Example embodiments are described herein with reference to blockdiagrams and/or flowchart illustrations of computer-implemented methods,apparatus (systems and/or devices) and/or computer program products. Itis understood that a block of the block diagrams and/or flowchartillustrations, and combinations of blocks in the block diagrams and/orflowchart illustrations, can be implemented by computer programinstructions that are performed by one or more computer circuits. Thesecomputer program instructions may be provided to a processor circuit ofa general purpose computer circuit, special purpose computer circuit,and/or other programmable data processing circuit to produce a machine,such that the instructions, which execute via the processor of thecomputer and/or other programmable data processing apparatus, transformand control transistors, values stored in memory locations, and otherhardware components within such circuitry to implement thefunctions/acts specified in the block diagrams and/or flowchart block orblocks, and thereby create means (functionality) and/or structure forimplementing the functions/acts specified in the block diagrams and/orflowchart block(s).

These computer program instructions may also be stored in a tangiblecomputer-readable medium that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablemedium produce an article of manufacture including instructions whichimplement the functions/acts specified in the block diagrams and/orflowchart block or blocks. Accordingly, embodiments of present inventiveconcepts may be embodied in hardware and/or in software (includingfirmware, resident software, micro-code, etc.) that runs on a processorsuch as a digital signal processor, which may collectively be referredto as “circuitry,” “a module” or variants thereof.

It should also be noted that in some alternate implementations, thefunctions/acts noted in the blocks may occur out of the order noted inthe flowcharts. For example, two blocks shown in succession may in factbe executed substantially concurrently or the blocks may sometimes beexecuted in the reverse order, depending upon the functionality/actsinvolved. Moreover, the functionality of a given block of the flowchartsand/or block diagrams may be separated into multiple blocks and/or thefunctionality of two or more blocks of the flowcharts and/or blockdiagrams may be at least partially integrated. Finally, other blocks maybe added/inserted between the blocks that are illustrated, and/orblocks/operations may be omitted without departing from the scope ofinventive concepts. Moreover, although some of the diagrams includearrows on communication paths to show a primary direction ofcommunication, it is to be understood that communication may occur inthe opposite direction to the depicted arrows.

Many variations and modifications can be made to the embodiments withoutsubstantially departing from the principles of the present inventiveconcepts. All such variations and modifications are intended to beincluded herein within the scope of present inventive concepts.Accordingly, the above disclosed subject matter is to be consideredillustrative, and not restrictive, and the examples of embodiments areintended to cover all such modifications, enhancements, and otherembodiments, which fall within the spirit and scope of present inventiveconcepts. Thus, to the maximum extent allowed by law, the scope ofpresent inventive concepts are to be determined by the broadestpermissible interpretation of the present disclosure including theexamples of embodiments and their equivalents, and shall not berestricted or limited by the foregoing detailed description.

1-26. (canceled)
 27. A method of operating a wireless device in acommunication network, the method comprising: receiving a schedulingmessage including a Downlink Control Indication, DCI, that includes aschedule identifying a plurality of transmission blocks, TBs;determining a quantity of the plurality of TBs that are identified inthe DCI; determining a quantity of Hybrid Automatic Repeat RequestAcknowledgement, HARQ ACKs in an ACK bundle identified in the DCI; anddynamically generating an acknowledgement timer value that correspondsto the quantity of the plurality of TBs and the quantity of HARQ ACKs inthe ACK bundle, characterized in that the acknowledgement timer valuecomprises a Hybrid Automatic Repeat Request Round Trip Time, HARQ RTT,timer value that is generated as 7+N*m in which N is a Physical UplinkControl Channel, PUCCH, repetition factor, and m is the number of HARQACK bundles identified in the scheduling message.
 28. The method ofclaim 27, wherein the communication network comprises a narrow bandinternet of things network, NBIoT.
 29. The method of claim 27, whereinthe communication network comprises an enhanced Machine TypeCommunication, eMTC, network.
 30. A wireless device adapted to performthe following steps: receiving a scheduling message including a DownlinkControl Indication, DCI, that includes a schedule identifying aplurality of transmission blocks, TBs; determining a quantity of theplurality of TBs that are identified in the DCI; determining a quantityof Hybrid Automatic Repeat Request Acknowledgement, HARQ ACKs in an ACKbundle identified in the DCI; and dynamically generating anacknowledgement timer value that corresponds to the quantity of theplurality of TBs and the quantity of HARQ ACKs in the ACK bundle,characterized in that the acknowledgement timer value comprises a HybridAutomatic Repeat Request Round Trip Time, HARQ RTT, timer value that isgenerated as 7+N*m in which N is a Physical Uplink Control Channel,PUCCH, repetition factor, and m is the number of HARQ ACK bundlesidentified in the scheduling message.
 31. A computer program comprisingprogram code to be executed by processing circuitry of a wirelessdevice, whereby execution of the program code causes the wireless deviceto perform operations according to claim
 27. 32. A computer programcomprising program code to be executed by processing circuitry of awireless device, whereby execution of the program code causes thewireless device to perform operations according to claim
 28. 33. Acomputer program comprising program code to be executed by processingcircuitry of a wireless device, whereby execution of the program codecauses the wireless device to perform operations according to claim 29.34. A computer program product comprising a non-transitory storagemedium including program code to be executed by processing circuitry ofa wireless device, whereby execution of the program code causes thewireless device to perform operations according to claim
 27. 35. Acomputer program product comprising a non-transitory storage mediumincluding program code to be executed by processing circuitry of awireless device, whereby execution of the program code causes thewireless device to perform operations according to claim
 28. 36. Acomputer program product comprising a non-transitory storage mediumincluding program code to be executed by processing circuitry of awireless device, whereby execution of the program code causes thewireless device to perform operations according to claim
 29. 37. Amethod in a communication network system, comprising a radio accessnetwork, RAN, node and a wireless device, the method comprising:sending, by the RAN node to the wireless device, a scheduling messageincluding a Downlink Control Indication, DCI, that includes a scheduleidentifying a plurality of transmission blocks, TBs; receiving, by thewireless device from the RAN node, the scheduling message including theDCI; determining, by the wireless device, a quantity of the plurality ofTBs that are identified in the DCI; determining, by the wireless device,a quantity of Hybrid Automatic Repeat Request Acknowledgement, HARQ ACKsin an ACK bundle identified in the DCI; and dynamically generating, bythe wireless device, an acknowledgement timer value that corresponds tothe quantity of the plurality of TBs and the quantity of HARQ ACKs inthe ACK bundle, characterized in that the acknowledgement timer valuecomprises a Hybrid Automatic Repeat Request Round Trip Time, HARQ RTT,timer value that is generated as 7+N*m in which N is a Physical UplinkControl Channel, PUCCH, repetition factor, and m is the number of HARQACK bundles identified in the DCI.
 38. A communication network system,comprising a radio access network, RAN, node and a wireless device, theRAN node sends, to the wireless device, a scheduling message including aDownlink Control Indication, DCI, that includes a schedule identifying aplurality of transmission blocks, TBs; the wireless device receives,from the RAN node, the scheduling message including the DCI; thewireless device determines a quantity of the plurality of TBs that areidentified in the DCI and a quantity of Hybrid Automatic Repeat RequestAcknowledgement, HARQ ACKs in an ACK bundle identified in the DCI, anddynamically generates an acknowledgement timer value that corresponds tothe quantity of the plurality of TBs and the quantity of HARQ ACKs inthe ACK bundle, characterized in that the acknowledgement timer valuecomprises a Hybrid Automatic Repeat Request Round Trip Time, HARQ RTT,timer value that is generated as 7+N*m in which N is a Physical UplinkControl Channel, PUCCH, repetition factor, and m is the number of HARQACK bundles identified in the DCI.